Odoo Customization Services in Turkey
Custom code is a liability you agree to carry. We keep it small, keep it in its own module, and write it so the next upgrade does not eat it.
What changes the cost of Odoo customization in Turkey
The delivery method is the same everywhere. What moves the number is what this market demands of the system, and how much of that Odoo already covers.
Turkey runs e-Fatura (e-Invoice) and e-Arşiv (e-Archive), part of GİB's e-Belge (e-Document) family. That is configuration and testing work inside the build, not an afterthought, and it is the item most often left out of a quote.
12 of the 17 payment options that matter in Turkey are not shipped with Odoo, so they need a paid connector or a build. 5 ship in the box.
10 of the 13 couriers used in Turkey have no Odoo connector. 3 do. Which ones you actually use changes the estimate more than the number of users does.
Odoo's Turkey localization does not cover everything. The gaps are listed on the country page and each one is either a build or a bought module.
Statutory payroll in Turkey has its own rules. Whether Odoo ships a payroll localization for this market decides if that is configuration or development.
Market facts on this page checked on 22 August 2026 by Waqas Riasat, Way4Tech.
Where Turkey starts from
Turkey has 6 native localization items in Odoo and 6 documented gaps beyond them. Customization work here usually starts at that gap list, not from a blank module.
Where we deliver in Turkey
Customization does not change shape by city. The brief is written the same way for a team in Istanbul as for one in Gaziantep: what the process actually is today, and where Odoo's default flow does not match it. Istanbul, Ankara, Izmir, Bursa, Antalya, Konya and Gaziantep are covered.
What odoo customization has to satisfy in Turkey
The rules that decide how much of this is configuration and how much is a build. Everything below is from our Turkey register, checked against a primary source.
Turkiye has run mandatory e-invoicing for years and the threshold rolls forward every year. Taxpayers with 2025 gross sales of TRY 3 million or more were required to be on e-Fatura by 1 July 2026, a deadline that has now passed. The rule is standing rather than one-off, so the next annual transition date applies to whoever crosses the threshold next.
- Centralised continuous transaction control. e-Fatura documents route through GİB infrastructure, either the GİB portal or a licensed özel entegratör (private integrator). This is not a file you drop on a portal once a month.
- UBL-TR 2.1 XML.
- Mandatory electronic signature. Companies sign with a mali mühür (financial seal) certificate; documents from New Generation payment recording devices (YN ÖKC) are signed with the device's fiscal certificate.
- e-Arşiv covers everything outside the e-Fatura mailbox system, including B2C and export, and is reported to GİB rather than exchanged.
- Archiving: 5 years under tax law and 10 years under commercial law. Archiving outside Türkiye is not permitted, which constrains where the database and its attachments can be hosted.
- Accounting e-Defter is GİB's electronic ledger system. It covers the yevmiye defteri (journal), büyük defter (general ledger) and envanter defteri (inventory ledger). Ledger files and their berat files are uploaded to GİB, either monthly or per provisional tax period, and GİB has extended deadlines by circular more than once.
- Accounting Odoo ships the Turkish chart of accounts, taxes, financial reports and fiscal positions in l10n_tr, with Türkiye-specific tax and profit and loss reporting in l10n_tr_reports.
- Accounting Books and records must stay retrievable for 5 years under tax law and 10 years under commercial law, and cannot be archived outside Türkiye.
- Accounting The Tekdüzen Hesap Planı (Uniform Chart of Accounts) is the standard account structure used across Turkish businesses. The Public Oversight Authority (KGK) put a separate chart of accounts aligned to financial reporting standards into force on 30 July 2024, sitting alongside it.
- Payroll Social security is administered by SGK. As of 1 January 2026 the employee pays 14% social security plus 1% unemployment insurance. Contributions are calculated on monthly earnings between TRY 33,030.00 and a ceiling of TRY 297,270.00.
- Payroll The employer pays 20.75% social security plus 2% unemployment insurance, with reductions available in some cases (16.75% under certain conditions, 5% for manufacturing). The state adds 1% to unemployment insurance.
- Payroll Stamp tax of 0.759% is withheld on gross salary payments, so payroll has three statutory deductions to model, not two: income tax, social security and stamp tax.
- Turkish chart of accounts, taxes, financial reports and fiscal positions.
- Türkiye-specific tax and profit and loss reporting.
- e-Fatura and e-Arşiv through Nilvera: GİB-compliant XML generation, transmission to Nilvera, and document plus status synchronisation back into Odoo.
- Invoice scenarios for basic, public sector (kamu) and export, covering sales, withholding (tevkifat), export-registered (ihraç kayıtlı) and tax-exempt (istisna) cases.
- e-İrsaliye dispatch note generation and upload.
- e-Defter (e-Ledger) output.
- The whole e-document path is tied to Nilvera as the özel entegratör. If the client is already contracted to Logo, Uyumsoft, QNB eFinans, İzibiz or Sovos, none of that is in Odoo. Either migrate them to Nilvera or budget a connector. This is the single biggest scoping question on a Turkish project and it is worth asking in the first call.
- Only e-Fatura, e-Arşiv, e-İrsaliye and e-Defter are covered. e-SMM, e-Müstahsil Makbuzu, e-Bilet and YN ÖKC device integration are not, so professional services firms, agricultural buyers and ticketing businesses need extra work.
- Hosting. Archiving outside Türkiye is not permitted, so check where the Odoo database, filestore and attachments physically sit before signing anything. This can rule out a default cloud region.
- Master data cleanup. VKN/TCKN, tax office and Mersis are mandatory on partners and are almost always incomplete in the data being migrated. Plan the cleanup as its own workstream.
- No Turkish courier ships natively. Budget a paid connector per carrier, or a free community multi-carrier module that you have actually tested.
Reviewed 2026-08-22. The full Turkey register
How we run the work
5 stages, the same in every market: Requirement capture, Technical specification and estimate, Build in sprints, Test and review, Deploy and hand over. The method does not change by country, so it is written up once rather than repeated here.
The integrations this market usually needs
Badged by what it takes in Odoo. Anything not marked In Odoo is a paid connector or a build, and that is the part quotes usually miss.
Questions we get asked
- Will customisation break our next Odoo upgrade?
- Well-written custom modules do not break, they need porting, and the effort depends on how deeply they reach into standard behaviour. Code that extends existing models ports quickly. Code that replaces standard logic is expensive at every version. That is the single biggest reason we push back on requests that duplicate what Odoo already does.
- Do we own the code?
- Yes. Source goes to your repository with the commit history intact, plus build and deploy instructions. There is no licence key, no time bomb and no obfuscation. If you replace us, the next team can read what we wrote.
- Does Odoo have an official localization for Turkey?
- Yes. Odoo ships 6 native items for Turkey, covering the basics of the chart of accounts and statutory setup. 6 areas are still outside that localization and get built or bought separately.
- Is e-invoicing mandatory in Turkey?
- Turkiye has run mandatory e-invoicing for years and the threshold rolls forward every year. Taxpayers with 2025 gross sales of TRY 3 million or more were required to be on e-Fatura by 1 July 2026, a deadline that has now passed. The rule is standing rather than one-off, so the next annual transition date applies to whoever crosses the threshold next. The Turkey e-invoicing page carries the full detail and the sources.
- What VAT or sales tax does Odoo have to handle in Turkey?
- VAT (KDV) is the indirect tax. The standard rate is 20%. Reduced rates are 10% for List No. II items such as basic foodstuffs, textiles and books, and 1% for List No. I items such as raw cotton and dried hazelnuts.
- Do you work with businesses in Istanbul and other parts of Turkey?
- Yes. Odoo customization runs remotely by default, and being based in one city inside Turkey does not change the plan or the price. Cities we cover for on-site visits: Istanbul, Ankara, Izmir, Bursa, Antalya, Konya, Gaziantep. We travel on-site for discovery workshops and go-live week when the engagement calls for it.