Five years ago a self-service customer portal was a "nice-to-have" enterprise feature. In 2026 it's becoming table stakes for Turkish SMEs — particularly those selling B2B to chain retailers, large industrial buyers or government procurement (KİK). When Migros, BIM, A101 or a Tier-1 manufacturer wants to know "where is my order, what's my account balance, send me last month's invoice copies," they don't want to call your finance office at 11am — they want a portal at 11pm. This article explains why, how, and what mistakes to avoid.
What a portal actually replaces
Three types of incoming traffic shift from human channels (phone, WhatsApp, email) to self-service:
Customer portal traffic
- Account balance & ageing inquiries
- Order status (placed → confirmed → shipped → delivered)
- Dispatch ETA and tracking
- Invoice copies (e-Fatura PDF or e-Arşiv link)
- Statement of accounts (extre)
- Mutual reconciliation (mutabakat) request/response
- Past purchase history and reorder
- Returns and complaints intake
Supplier portal traffic
- Purchase order copies and acknowledgement
- Delivery booking calendar
- Invoice submission with auto-validation
- Payment status and remittance advice
- Quality non-conformance feedback
- New supplier onboarding documents
Employee self-service (different scope, mentioned for context)
- Leave requests, payslips, expense claims, performance review
The economic case
For a 50-person Türkiye SME doing B2B sales:
| Metric | Without portal | With portal | Annual saving |
|---|---|---|---|
| Customer service inbound (calls + emails / month) | 1,800 | 1,100 | ₺ 180,000 (1 fewer FTE × 12) |
| Average days sales outstanding (DSO) | 73 days | 61 days | ₺ 600,000 (working capital release) |
| Mutual reconciliation cycle time | 9 days | 2 days | ₺ 50,000 (audit prep saved) |
| Invoice dispute resolution | 22 days avg | 6 days avg | ₺ 80,000 (collections improvement) |
Total: roughly ₺ 900,000/year in saved cost + working capital release, against a portal operating cost of ~₺ 30-60k/year. The payback is 2-3 months.
Why now in Türkiye specifically
Three forces make 2026 the right adoption window:
1. Chain-retailer pressure. Migros, BIM, A101 and the rest now grade their suppliers on portal availability. A reliable supplier portal is increasingly part of supplier-onboarding scoring; some chains add a discount-back clause for suppliers without one.
2. Mutual reconciliation discipline. With BA-BS being phased out (replaced by mutual reconciliation between parties), the volume of monthly reconciliation requests is exploding. Doing this by email at 200+ counterparties per month is not sustainable; portals automate the workflow.
3. KOSGEB grant eligibility. Self-service portals (both customer and supplier) qualify as digital transformation under KOSGEB's 70% grant — meaning you pay 30% of the licence + setup.
Implementation patterns that work
A) Embedded in your ERP. Portal data flows directly from the ERP without batch exports — order status, ageing, invoice copies are live, not yesterday's snapshot. No middleware. This is the lowest-risk pattern.
B) Branded, per-customer. Each large customer sees their logo, their colour scheme, their preferred document format. Especially important when bidding to a chain — they want to feel the supplier "speaks their brand."
C) Bilingual TR + EN. Foreign buyers and Turkish-domestic users see the right language without admin work. (DE / FR / ES configurable for European buyers.)
D) WhatsApp Business hand-off. When self-service hits its limit ("I want to place a custom order"), one tap escalates to a WhatsApp Business chat with your sales rep. Don't force users to switch channels manually.
Implementation patterns that fail
1. Built as a separate microsite that pulls from the ERP nightly. Customers see stale data, lose trust, go back to phoning your finance team.
2. No mobile responsiveness. 60%+ of B2B portal traffic in Türkiye is mobile. A desktop-only portal is dead on arrival.
3. SSO-required for every login. Foreign customers don't have your SSO; their procurement officer needs a simple username + 2FA. Internal users get SSO via their Microsoft 365.
4. No audit trail. When a customer disputes "I asked for delivery on the 15th, you delivered on the 20th," you need a portal-side log showing what they actually requested.
Birasyo's portal modules
Birasyo ships two distinct portal modules, both included in the Professional plan:
- Customer Portal — branded per customer, bilingual TR + EN (other languages on request), live ERP data, dispatch tracking, invoice copies (e-Fatura + e-Arşiv), mutual reconciliation workflow, payment status, KVKK-compliant consent management, WhatsApp escalation hook.
- Supplier Portal — purchase order acknowledgement, delivery booking, invoice submission with UBL-TR validation, payment status, non-conformance feedback, supplier onboarding wizard.
Both portals run on the same Azure Europe infrastructure as the main ERP, with the same KVKK compliance and audit trail. They're available standalone for customers using a different ERP — connecting via REST API.
Closing
A self-service portal isn't a "future" feature in 2026 Türkiye — it's already affecting whether large B2B customers choose to source from you or move to a more digitised competitor. The cost case alone (saved support hours, faster collections) justifies the investment; the strategic case (chain-retailer scoring, KOSGEB grant, foreign-buyer competitiveness) makes it urgent.
Want a demo with a real Birasyo customer portal you can click through? We'll walk through both customer and supplier modules and quote the KOSGEB application pack at no cost.
Related reads:
Share this on LinkedIn
Headline, summary and hashtags copy to your clipboard and the LinkedIn composer opens — paste (Cmd/Ctrl+V) and post.
