Food Delivery Software in Türkiye — Launch Your Platform
Türkiye is a dense, mobile-first delivery market dominated by Yemeksepeti, Getir and Trendyol Go. The opportunity is not another Istanbul-wide app; it is a focused district or city where restaurants want their own ordering channel.
The market shape
Istanbul, Ankara and Izmir have the deepest restaurant supply and the strongest competition. Secondary cities such as Bursa, Antalya and Konya have weaker aggregator coverage but fewer organised restaurants. Start with one dense district — Kadıköy, Beşiktaş or Şişli in Istanbul — and prove order density before expanding.
Food inflation and currency movement make unit economics volatile. Set commission and delivery fees so they can be reviewed monthly, and keep a cash buffer for fuel and rider costs.
Payments
Cards and cash are both common. iyzico and PayTR are the local gateways most restaurants ask for; neither is in the standard Foodomaa gateway list, so they are paid custom integrations. You need a merchant account, 3-D Secure and a test plan for instalments, refunds and failed payments. Stripe and PayPal are available as standard but do not cover every local card behaviour.
Turkish language and KVKK
The package includes a Turkish notifications file, not a complete native Turkish interface. The source code and language files can be translated, but budget a native review of the storefront, apps, emails and invoices. KVKK data-protection rules apply; confirm hosting, retention and consent with local counsel.
Rider economics
Fuel, insurance and minimum-wage rules decide the delivery cost. Scooter riders work well in dense districts; a 3–4 km radius is usually more realistic than a city-wide map. If you use cash, set a per-rider limit and reconcile at the end of every shift.
Launch plan
- Pick one district with 25–40 takeaway restaurants and a clear customer segment.
- Prepare the Turkish storefront, legal pages and payment integration.
- Run 30 test orders, including one refund, one failed payment and one rider reassignment.
- Soft-launch to one customer group; review every order manually for two weeks.
Costs
The licence is $299 once, plus a VPS, gateway fees, SMS, maps and any custom payment work. There is no monthly licence fee and no commission to Foodomaa. Compare that with the commission of a national aggregator before promising restaurants a lower rate.
Türkiye questions
Is iyzico or PayTR included?
No. Both are paid custom integrations. We confirm scope after reviewing your merchant account and their API documentation.
Is Turkish included?
A Turkish notifications file is included, but the full interface needs translation and native review. Budget that as a separate task.
Is cash on delivery supported?
Yes, with per-rider cash limits and end-of-shift reconciliation.
Which city should I start in?
One dense Istanbul district, or a secondary city with strong restaurant supply and weak aggregator coverage.
Is KVKK compliance included?
No. The software can be configured for data protection, but KVKK compliance depends on your contracts, hosting and processes. Confirm with local counsel.
What to configure first
- Currency and commission: set TRY, the vendor commission and the delivery fee together; review monthly against inflation.
- Zones: start with one 3–4 km district, not the whole city. Test an address at each edge.
- Payments: keep cash on delivery and add card/iyzico or PayTR only after the merchant account is approved.
- Turkish copy: translate the customer journey first, then vendor and rider strings; native review before launch.
- KVKK: document data retention, consent and processor agreements before importing customer data.
Common launch mistakes
- Launching across Istanbul instead of one district with 25–40 restaurants.
- Promising a 20-minute delivery time before rider supply is proven.
- Ignoring cash reconciliation because card payments are growing.
- Using machine-translated checkout copy and losing trust at payment.
- Underestimating fuel, insurance and rider idle time in the commission model.
A 90-day sequence
- Days 1–20: choose the district, sign 20–30 restaurants, prepare Turkish copy and legal pages.
- Days 21–40: configure zones, commission, cash limits and the payment integration.
- Days 41–60: recruit riders, run 30 test orders and fix the three most common failures.
- Days 61–75: soft-launch to one customer group; measure delivery time and repeat rate.
- Days 76–90: add a second district only if the first is stable and contribution-positive.
Who this fits
- A restaurant group in Istanbul, Ankara or Izmir that wants its own ordering channel and customer data.
- A district-level marketplace with 25–40 restaurants and a controlled rider fleet.
- A cloud kitchen running two or three delivery-only brands from one line.
- An operator with a local partner who can handle Turkish copy, KVKK and merchant onboarding.
What to ask before buying
- Which parts of the Turkish interface are translated, and who reviews them?
- What is the exact iyzico/PayTR scope, and who owns the merchant account?
- How will cash limits and end-of-shift reconciliation work?
- Which KVKK documents and processor agreements are required?
- What is the rider employment/insurance model in the launch city?
Three ways to start
| Model | Best for | What changes |
|---|---|---|
| Single-brand restaurant | A restaurant with repeat customers | One menu, one zone, pickup plus delivery |
| District marketplace | An operator who can sign 25–40 restaurants | Commission, vendor onboarding, shared riders |
| Cloud kitchen | Two or three delivery-only brands | Per-brand menus, shared kitchen queue and riders |
Start with the model that matches the supply you can sign in 30 days, not the model that sounds largest in a pitch.