SultanaExpress
Beta — September 2026 · Türkiye first, Europe next

Why this market. Why now. Why us.

SultanaExpress is a B2B sourcing platform for Turkish manufacturing. The thesis in three sentences: Türkiye ships industrial goods into the EU at zero customs duty, days away by road. Four EU regulations will force every textile supplier selling into that market to produce structured product data, on dated deadlines between 2026 and 2028. We are the team that already ran a marketplace in this market — and we are rebuilding it so the transaction itself, not the directory listing, is the product.

All figures as of 2026-08-01. A source is named wherever a number appears.

01 · The corridor

Zero duty. Days away. Still offline.

The ground under the thesis is structural, and every number on it is primary-sourced.

  • 0%customs duties on industrial goods — textiles and apparel included — under the EU–Türkiye Customs UnionEuropean Commission
  • $117Bof goods exported from Türkiye to the EU in 2025official Turkish trade data, full-year 2025
  • 3–7 daystypical road freight Türkiye→EU, against 58.2 days ocean China→North Europeforwarder-quoted lanes; Flexport Ocean Timeliness Indicator, week to 27 Jul 2026
  • 7thlargest apparel exporter in the worldİHKİB / Trademap

The buyers are already moving this way.

CBI — the Dutch government's import-promotion agency — names the brands nearshoring production to Türkiye: Inditex, H&M, Bestseller, Mango. Türkiye is one of the twelve production clusters where Inditex concentrates roughly 92% of its output. The same CBI analysis states that European buyers want "smaller production runs" from nearer countries. That sentence is our MOQ-and-capacity thesis, written by a government agency instead of by us.

We will say the uncomfortable part ourselves.

Turkish textile and apparel exports fell 4.4% in 2025, to $26.18B (İHKİB/İTHİB). This is not a growth-market pitch and we will not dress it as one. It is a margin-compression story: the thesis does not need the market to grow — it needs the trade to change channel. A manufacturer losing share and facing a compliance-data mandate needs direct digital demand and provable provenance more, not less.

[PENDING-PIN G3 — do not publish this block until pinned. The Türkiye→EU textile+apparel corridor computes to ~$14.5B (2025); it must be pinned to a Eurostat Comext / İHKİB primary series first. Copy once pinned: "$14.5B — the Türkiye→EU textile and apparel corridor (2025), per Eurostat Comext/İHKİB."]

02 · The engine

Four EU regulations. Four dates. This is the demand engine.

Between 2026 and 2028 the EU obliges every company selling textiles into it to produce structured product and supplier data. Most of Türkiye's supplier base is offline and fragmented; the data the law demands does not exist in structured form today. Something has to bring it into existence. That something is the platform.

  1. IN APPLICATION

    ESPR: destroying unsold textiles is banned

    Since 19 July 2026, large companies may no longer destroy unsold clothing and footwear in the EU. Exemptions must be documented, reported annually, and kept on record. The first hard deadline has already passed — two weeks before this page's stamp. Source: European Commission.

  2. TRANSPOSING NOW

    Textile EPR in all 27 member states

    The revised Waste Framework Directive entered into force on 16 October 2025. Every member state must establish an extended-producer-responsibility scheme for textiles and footwear within 30 months. Producers pay the fees that finance collection, reuse and recycling. Source: European Commission.

  3. APPLIES TO EVERY COMPANY SIZE

    EU Forced Labour Regulation

    All products, all sectors, no size threshold. A Turkish SME selling into the EU is inside the perimeter. Compliance rests on due diligence and supply-chain traceability — which means data. Source: Regulation (EU) 2024/3015.

  4. DELEGATED ACT PENDING

    Digital Product Passport for textiles

    Textiles lead the priority product groups of the ESPR working plan. The delegated act that carries the textile DPP is indicatively due in 2027. Source: European Commission.

None of these regulations asks a supplier's opinion. Each demands data — provenance, materials, certifications, chain of custody — in structured form. A platform that already holds the tech pack, the certificate register, the verified company identity and the transaction record produces that data as a by-product of doing the trade.

03 · The structural gap

Matchmaking was never the hard part.

For a decade, sourcing platforms treated this as a search problem: build a directory, sell subscriptions or one-time listing fees, and leave the actual trade — the money, the sample, the capacity slot, the inspection — to email and hope. Several of the category's best-funded companies shut down or pivoted between 2022 and 2024. The economics explain it: a directory gets paid whether or not the trade succeeds, so the product never has to own the trade.

Nobody in this tier prices the transaction. The prevailing models are subscriptions and one-off fees. The transaction itself — where the risk sits and where the value is — stays unmonetized because it stays un-owned. Meanwhile the real incumbent is offline: the trade fair and the sourcing agent.

Our claim is precise. The pieces exist across the market — escrow in one place, inspections in another, directories everywhere. What does not exist is a platform where escrow on a real ledger, sample-gated production, bookable factory capacity and AQL quality control are native, self-serve product primitives inside one transaction flow. We claim that combination — and we build each piece as a mechanism the server enforces, not a service layer. The server refuses a sub-minimum order. Bulk production cannot start before the approved sample — the platform returns a refusal.

04 · The team

We ran this market before we built for it.

We built and operated a production marketplace in exactly this market: buyer and supplier iOS apps, real users. Then we audited our own system line by line — 106 tables, 341 stored procedures, 687 row-level-security policies, 228 catalogued features — and found the failure modes. The rebuild does not merely fix them; it makes each one impossible by construction.

Four founders

  • Louis Loubes — CEO
  • Abdullah Kahvecioglu — CTO
  • Leonard Loubes — COO
  • Tatiana Loubes — CFO

The engineering proof

Counted by direct audit of the repositories on 2026-08-01. Re-derived at every publish — these numbers move weekly. The running history lives on our Building in the Open page.

  • 649numbered steps in the published build plan — 304 complete, the hardest and least reversible half first
  • 24 daysfrom the backend repository's first commit (8 July 2026) to every number below
  • 125k + 106klines of production Go + lines of tests (a 0.85:1 ratio) — 1,666 test functions, 157 database migrations, 37 modules
  • 346operations in one OpenAPI 3.1 contract, plus 108 event channels each pinned to a frozen byte-exact sample message
  • 52merge-blocking automated checks across backend and web — 31 of them business-rule checks written for this platform: money must balance to the kuruş, no query can read another company's data, personal data never reaches a log line
  • 2,650findings from 443 independent AI review passes — 58 critical — all caught and fixed before merge, all on the permanent record
  • 2,822approved reference screenshots; every change is compared against them at three widths, in light and dark, left-to-right and right-to-left
  • 1.65Mwords of committed plan — 44 architecture decision records, 44 module specifications — written before and during the build

One rule is enforced in code, not policy: no AI review can ever be a required merge check. A test fails the build if one appears in the branch protection. Where money or personal data is concerned, the authority is always a deterministic test.

Compliance-native, by data model

The platform's core records already have the shape the EU regulations demand. Immutable, versioned tech packs pin exact material specifications. Certifications carry issuer and expiry and are tracked down to the document. Company identity is verified — KYB, never self-declared. Every order links a spec version, a sample approval, an inspection result and a payment. When the textile Digital Product Passport delegated act lands, its fields map onto rows we already keep. We do not claim a live DPP — we claim a data model shaped for it from the first migration.

05 · Status & the ask

Where the build stands

Built and merged

Backend: accounts, catalog, pricing, inventory, ordering, the double-entry money ledger, the manufacturing spec-and-capacity chain, quality control, search, messaging, certifications, reviews and shipping — 37 modules, all behind the automated check wall. Web: the design system, the component library, and the supplier workspace from catalog through pricing, RFQ and orders, with the capacity screens in build (phase 112). The whole stack runs today against a self-hosted Kubernetes data plane, locally. We do not claim production traffic — there is none yet, by design.

Ahead

The operator console, the remaining cross-border and reporting modules, the production cluster, then go-live.

Real money turns on last. Live payments are gated behind sign-off from payment counsel, our CPA and the payment provider. Those answers block go-live — they never block the build. The day they arrive, the switch is a configuration change against already-proven code.

The ask

Beta opens September 2026 — Türkiye first as the test market, Europe next. If a zero-duty corridor, a dated compliance clock and a build you can audit read as a thesis to you, talk to us. Louis Loubes (CEO) leads investor relations.

investors@sultana.express — read and answered by Louis Loubes, CEO. investors@sultana.express · Request data-room access: investors@sultana.express.