Multi-Branch and Multi-Warehouse Architecture for Turkish Subsidiaries (2026)

Your Turkish subsidiary started in İstanbul. After 18 months, sales in Ankara and İzmir are taking off, the operations director wants a second warehouse in Kocaeli, and the CFO is pushing for cost-center P&Ls per region. Suddenly your ERP setup, designed for "one entity, one location," is creaking. The choices you make at this moment shape how easily you can grow for the next five years.

This guide walks foreign-owned Türkiye subsidiaries through the multi-branch / multi-warehouse architecture decisions, with focus on Türkiye-specific considerations that an HQ playbook from elsewhere won't capture.

Note: Türkiye-specific tax and operational rules change. Confirm with your CPA for your specific situation.

Three concepts to keep separate

A frequent mistake is conflating these three:

Branch (Şube) — Organisational and sometimes tax-relevant unit. A branch may share the same legal entity (single tax registration) or be a separate registration. Sales, marketing, customer service typically tied to a branch.

Warehouse (Depo) — Physical inventory location. One branch may have multiple warehouses; multiple branches may share one warehouse.

Cost / Profit Center — Accounting dimension. A "cost center" in your chart of accounts that lets you produce a P&L per region, per product line, or per major customer segment.

These three are independent. Your ERP must allow many-to-many relationships among them. Conflating "branch = warehouse = cost center" works in a small operation but breaks at scale.

Türkiye-specific considerations

1. Inter-branch goods transfers and KDV

Moving goods from your İstanbul warehouse to your Ankara warehouse (same legal entity) is not a sale, but Turkish tax practice still expects an internal waybill (sevk irsaliyesi) documenting the transfer. The waybill flows through e-İrsaliye if you're enrolled. KDV is not charged on internal transfers but the documentation must be impeccable.

Pitfall: treating internal transfers as "casual paperwork." Inspectors look for missing waybills as evidence of inventory control weakness, even if no tax is due.

2. Same legal entity vs. separate entity branches

You can operate multiple cities under one Türkiye Limited Şirketi (LLC) with all branches as non-tax-separate units, OR you can incorporate separate LLCs per region. The trade-offs:

Aspect	Single entity, multiple branches	Separate entity per region
Tax registration	One tax number	One per entity
Inter-region transfer	Internal (no VAT)	Inter-company sale (VAT applies)
Reporting consolidation	Native to ERP	Requires consolidation logic
HR / Payroll	Single SGK registration	Separate per entity
Liability isolation	None — single entity	Separate per entity
Setup cost	Low	High (separate incorporations)

Most foreign-owned subsidiaries use single-entity-multiple-branches. Move to separate entities only when liability isolation becomes a serious concern (typically heavy-asset, regulated industries).

3. Per-branch profit centers

Even within a single legal entity, your CFO will want per-branch P&Ls. The ERP must support dimensional accounting: each transaction tags with branch / cost center / department, and reports filter by these dimensions.

Without this, your CFO rebuilds it in Excel monthly.

4. Per-warehouse stock pools

Each warehouse should be a separate stock pool with its own quantity, cost layer, expiry tracking, and reservation rules. Cross-warehouse transfers happen via an explicit transfer document.

Some ERPs simplify this to "one global stock with location tags" — this seems convenient but breaks when you need warehouse-specific costing or inventory aging.

5. Branch-scoped user permissions

A branch manager in Ankara should NOT see İstanbul customer data, İzmir pricing, or HQ-level salaries. Modern ERPs implement this via row-level security: a user's role determines which records they can read or modify.

Without row-level security, the branch manager's "I won't look at the other data" is purely a policy promise — easily violated.

Architecture patterns by company size

Pattern A: Up to 50 employees, 2-3 warehouses, 1-2 branches Single legal entity, dimensional accounting (branch + cost-center), 3-warehouse setup with weekly transfer reconciliation.

Pattern B: 50-150 employees, multi-region operations Single legal entity, dimensional accounting with up to 6 cost centers, monthly per-branch P&L reporting, branch-scoped user permissions, dedicated warehouse for returns and quality holds.

Pattern C: 150+ employees, multiple major regions, possible separate entities Either single legal entity with sophisticated dimensional accounting + treasury netting, OR multiple legal entities with consolidation. At this size the choice depends on liability profile and regulatory specialty.

The 6 mistakes that derail expansion

1. "We'll add the second branch later in the same chart of accounts." Result: 12 months of mixed transactions you can't separate. Plan branches as dimensions from day one.

2. "Each branch can use its own pricing in Excel." Branch-specific pricing must be in the ERP with proper price-list management. Excel pricing leads to unauthorised discounts and customer complaints.

3. "Don't bother with warehouse transfers, just use stock adjustments." Stock adjustments without transfer documents create audit-log gaps. Inspectors may question the validity of inventory counts.

4. Mixing customer master data across branches. A customer should be one record (the entity buys from you), not three records (one per branch). Even if servicing differs, the entity is one. Use branch-specific contacts and pricing under one master.

5. Branch manager writes to corporate accounts. Without row-level security, a branch manager can accidentally edit customer records owned by another branch. KVKK exposure and operational chaos.

6. POS system not synced with central ERP at near-real-time. Branch POS that syncs once daily means stockouts at corporate ERP looking like stock-on-hand. Chain retailers expect 5-15 minute sync; below that, stock data is unreliable.

Implementation sequence

Phase 1: Dimensional accounting setup (week 1-2)

• Branch dimension added to chart of accounts
• Cost center dimension added (parallel or hierarchical)
• Mapping rules: each transaction must tag branch and cost center

Phase 2: Warehouse modelling (week 2-3)

• Each physical warehouse as separate stock pool
• Warehouse types: main, returns, quality hold, demo, consignment
• Transfer document workflow with status tracking

Phase 3: User permissions (week 3-4)

• Roles: HQ admin, branch manager, branch user, warehouse user, etc.
• Row-level security: each user sees only authorised branches
• Test thoroughly with non-admin user before go-live

Phase 4: Reporting (week 4-5)

• Per-branch P&L
• Per-warehouse inventory aging
• Per-cost-center expense tracking
• Consolidated views for HQ

Phase 5: Operational rollout (week 5-8)

• Train branch teams
• Run parallel with manual processes for 30 days
• Cut over

Birasyo's multi-branch architecture

Birasyo ERP supports:

• Independent dimensions: branch, warehouse, cost center, project — each can be combined in any way
• Row-level security: users see only authorised data based on role and branch assignment
• Internal transfer workflow: e-İrsaliye-compatible inter-warehouse transfers with status tracking
• Per-branch P&L out of the box, with consolidated views
• Multi-warehouse inventory with separate cost layers, aging, and reservation rules
• Branch-aware POS sync at 5-minute intervals or less

If you're scaling a Türkiye subsidiary into multiple branches or warehouses in 2026, book a 1-hour planning call — we'll map your specific operational footprint to an architecture pattern.

Related reads:

• Setting Up a Türkiye Subsidiary: Day-1 Checklist
• Multi-Currency ERP for Turkish Exporters
• ERP Selection Checklist for Foreign Investors in Türkiye