How to Integrate Logo ERP: Methods

Logo is a widely used ERP system in Turkey; according to Logo, more than 230,000 businesses run on its software. Yet many of these companies still enter the same information several times. E-commerce orders are re-entered into Logo manually, bank transactions are posted one by one and marketplace stock is updated separately. That takes time and invites mistakes. Integrating Logo removes the duplication: data is entered once and looks the same in every system.

This guide explains the official ways to connect Logo to your other systems (Logo Objects, the Logo REST service and XML transfer), the difference between off-the-shelf solutions and custom integration, and the steps of an integration project. It is written for companies that use common Logo products such as Tiger and Go, including Turkish subsidiaries of international groups, and for their IT teams.

The aim of integration is for data to flow between systems without being carried over by hand. Photo: Scott Rodgerson, Unsplash

What is Logo integration?

Logo integration means that Logo ERP and another piece of software exchange data automatically. An order placed on your online shop becomes a sales order in Logo, stock levels in Logo are reflected on the marketplace without manual updates, and bank transactions reach accounting without being retyped.

Without integration, the same data is keyed into several screens. Stock shows different figures in two places; an invoice is issued twice or not at all. The cost of the time spent tracking down these differences at month end often exceeds the cost of the integration itself.

Ways to connect Logo to other systems

Logo offers official interfaces for writing data into its products and reading it out. Which one to use depends on your Logo product, version and licence, and on what the connected system needs.

A quick note on names first: in September 2026 Logo restructured its product line. Fully cloud-based solutions are now grouped as Logo Cloud, while solutions that run on the customer's own servers, supported by cloud services, are grouped as Logo Edge. Product names such as Tiger, Go and Netsis are still used in Logo's support documentation, and this guide uses those familiar names. To find out which interfaces your version includes, ask your Logo business partner or check Logo's support documentation.

Logo Objects

Logo's support documentation describes Logo Objects as the COM interface for Tiger. An external application uses it to create and update records such as customer and supplier accounts, item cards, orders and invoices. Because records are created through Logo's own objects, this is a much safer route than writing to the database directly.

COM is a Windows-specific technology, so an integration built on Objects usually runs in the Windows environment where Logo is installed. On the Logo Edge T-Series product page, Objects is listed among the optional paid modules, so check whether your licence includes it before you start.

Logo REST service (REST API)

In Logo's words, the Logo REST service is a Logo ERP interface built on REST principles that makes the capabilities of Logo Objects available; it is supported in Logo's 3-series ERP products. REST is the most common way for web and mobile applications to communicate. Requests travel over HTTP, the integration can be written in any programming language, and it can run on a different machine from the one where Logo is installed.

If an online shop, a mobile app or a cloud system needs to talk to Logo in real time, this is usually the best route. Because the service relies on the capabilities of Objects, review its licensing and installation requirements alongside those of Objects.

Data transfer with XML

The Transfers (Aktarımlar) section of Logo Tiger can export records to XML files and import them back, and XML templates can be used in the process. This suits one-off transfers or periodic bulk operations. Because a file has to be prepared and imported each time, it is no substitute for a real-time, continuous integration.

Reading from the database

Logo keeps its data in an SQL database. Reading from that database with a read-only user is a common approach for reporting and business intelligence tools.

We do not recommend writing to the tables directly. Records written that way bypass Logo's official interfaces. Related records and the accounting side can end up inconsistent, and the problem often surfaces months later, during a reconciliation or a version upgrade. Use Objects or the REST service to create and update records.

Off-the-shelf solutions

Under the heading "Logo-approved ecosystem solutions", Logo's website presents ready-made products for areas such as marketplace and e-commerce integration, bank account management and warehouse management. One marketplace connector, for example, links Turkish marketplaces such as Trendyol, Hepsiburada, N11 and Pazarama, as well as common e-commerce platforms, to Logo ERP products. A bank statement solution transfers bank and card terminal (POS) transactions to Logo as bank or journal vouchers. According to Logo, more than 1,000 business partners help companies set up such solutions.

Method	Best for	Watch out for
Logo Objects	Integrations that create and update records in the Windows environment where Logo runs	Optional paid module; COM ties it to Windows
Logo REST service	Real-time integration with web, mobile and cloud applications	3-series products; uses Objects capabilities, so check the licence
XML transfer	One-off or periodic bulk transfers	Not real time; a file must be prepared each time
Reading from the database	Reporting and business intelligence	Read only; do not use it to create records
Off-the-shelf solution	Common scenarios such as marketplaces and banks	Must cover all your scenarios; subscription cost

The most common Logo integrations

Connected system	What is exchanged	Direction
Online shop and marketplaces	Orders, customers, stock, prices	Both ways
Bank	Account and POS transactions, collections and payments	Bank to Logo
Dealer (B2B) portal	Account balances, price lists, orders	Both ways
CRM	Customer records, quotes and orders	Both ways
Production and warehouse apps	Production slips, stock movements, stock counts	Mostly into Logo
Reporting and business intelligence	Sales, stock and finance data	Out of Logo, read only

Online shop and marketplaces. Orders arrive in Logo as sales orders or invoices, while stock and prices flow from Logo to the shop and the marketplace. The part that takes the most effort is making product codes match exactly on both sides. Products with variants such as colour and size make this matching even more important.

Bank. Banks provide account transactions through web services. The integration fetches the transactions using the web service access details provided by the bank and posts them to Logo. Collections reach customer accounts without manual entry, and month-end reconciliation takes less time.

E-invoice and e-archive. In Turkey, many businesses are required to issue invoices electronically through the tax authority's e-document system (e-Fatura, e-Arşiv). Logo has its own e-document products. If you send your invoices through another accredited provider, the connection is built on that provider's services.

Logo integration step by step

Map the data flow
Which data comes from where, where does it go, how often is it transferred and who uses it? Write down the direction and frequency.
Choose the method
Pick one of the official interfaces according to your Logo product, version and licence; consider an off-the-shelf solution if it meets the need.
Match the codes
Define in a table how account, item, warehouse, VAT rate and payment type codes correspond between the two systems.
Build in a test environment
Develop and test without touching live data, in a separate test company or a copy of the database.
Handle errors
Log every transfer, prevent the same record from being written twice, retry on failure and notify the right person.
Go live in a controlled way
Start with a limited set of data, compare the results by hand, then switch to the full flow.
Monitor and update An integration is a living system
Test the integration after every Logo version upgrade and review the logs regularly.

How we run a Logo integration.

Points to watch

Duplicate records: When a connection drops, the same order may be sent twice. Store a unique number from the external system with every record and check it before transferring.
Code matching: Most problems come from the data, not the technology; for example, a marketplace product code that does not exactly match the item code in Logo.
Permissions: The integration user should be able to perform only the operations it needs. Do not set up the integration with an administrator account.
Personal data: If customer data is transferred, keep a record of which data goes to which system, with Turkey's Personal Data Protection Law (KVKK) in mind.
Version upgrades: New versions can affect the integration. Try every upgrade in the test environment first.
Backup and rollback: Take a database backup before going live and decide in advance how you will roll back if something goes wrong.

Off-the-shelf or custom integration?

If your need is common, such as receiving orders from a few marketplaces or importing bank transactions, ready-made solutions from Logo business partners can be quick and economical. If your processes are non-standard, if you need to connect several systems at once or if you want your own application to talk to Logo, a custom integration is the better choice.

These questions help with the decision:

Does the ready-made solution cover all my scenarios, or will I have to bend my processes to fit it?
Who keeps the source code and the data?
When Logo is upgraded, who adapts the integration, and how fast?
How does a monthly subscription compare with a one-off development cost over several years?

Frequently asked questions

Does Logo Tiger have an API?

Yes. For Tiger, Logo provides a COM interface called Logo Objects and, in its 3-series products, the Logo REST service, which is built on REST principles and makes the capabilities of Objects available. Ask your Logo business partner which interface your product and licence include.

How long does a Logo integration take?

It depends on the scope. A one-way integration that transfers a single type of record, for example marketplace orders flowing into Logo, can go live within a few weeks. Projects that connect several systems in both directions take longer. Code matching and testing have the biggest effect on the timeline.

Can records be written directly to the Logo database?

Technically yes, but we do not recommend it. Records written directly do not pass through Logo's official interfaces, so related records and the accounting side can become inconsistent. Use the database for reading and reporting only.

Is an off-the-shelf marketplace connector enough?

If your product and order flows are standard, it usually is. If you have your own business rules, special pricing or several warehouses and companies, you may need a custom integration.

Does a Logo version upgrade affect the integration?

It can. Try the upgrade in the test environment first and apply it to the live system after checking the main integration flows.

If you would like to connect Logo to your online shop, your bank or your own applications, see our ERP integration page or get in touch; the first consultation is free.

How to integrate Logo ERP: methods, steps and pitfalls