How to Integrate Logo ERP with E-Commerce: A Guide for SMEs

Many businesses that run their accounting and inventory in Logo while also operating an online store or marketplace shop have days that look alike: orders are read off one screen in the morning, keyed into Logo by hand, delivery notes and invoices are issued, and in the evening stock figures are updated on the website one by one. When order volume is low, this works. As orders grow, a mistyped product code, a stock level that wasn't updated or an order entered twice starts to eat into the team's time and the customer's trust.

Logo e-commerce integration aims to remove that manual work. In this article we cover which data is synchronized in a Logo integration, the methods available along with their pros and cons, how it relates to the e-Invoice and e-Archive flow, the setup steps and the most common mistakes. It is written for SMEs using one of Logo's products such as Logo Tiger, Logo Go or j-Platform. Since there are technical differences between products and versions, we recommend always confirming the details for your own version with your Logo business partner.

What gets synchronized in a Logo e-commerce integration?#

An integration is not a single data flow but several flows with different directions and frequencies. Before you start, you need to be clear about which system is the "source of truth" for each type of data.

Stock#

Stock usually flows from Logo to the e-commerce side. The actual quantity in the warehouse is held in Logo, and the website or marketplace displays it. If there are multiple warehouses, decide in advance which ones are open for sale and whether reserved quantities should be deducted.

Prices#

In most businesses prices come from the price cards in Logo, but applying different prices on marketplaces to cover commissions is common. In that case a per-channel rule is applied to the list price in Logo, or a separate price list is kept for each channel.

Orders, delivery notes and invoices#

The most important data flowing the other way is orders. An order from the website or marketplace is transferred to Logo as a sales order; a delivery note is created on shipment, followed by the invoice. Some businesses prefer to turn the order straight into an invoice. Which steps are automatic and which require approval depends on your workflow.

Customer accounts#

The customer placing the order needs a customer account in Logo. Opening a new account for every individual customer produces thousands of records in a short time. That's why some businesses link individual sales to a shared account per channel, and use separate accounts matched by tax number for corporate customers. Which approach fits depends on your accounting and reporting needs; it's best decided together with your accountant.

Payments and bank transactions#

Payments by credit card, bank transfer or cash on delivery must be posted in Logo to the right customer account and the right ledger. Logo bank integration usually refers to importing bank account transactions into Logo and matching incoming payments with the relevant customer account or order. Payment providers often settle in batches with commission already deducted, which makes this matching the part that needs the most care.

Integration methods: pros and cons#

There are several ways to move data between Logo and e-commerce. Which one fits depends on your Logo product, its version, your license and your order volume.

Logo's official interfaces (Objects and REST services)#

Depending on the product and version, Logo provides official interfaces that let external systems read and write data. Logo Objects is an object library long used in the Tiger and Go family that creates records by running them through Logo's own business rules. Newer versions also include web-based REST services. An API integration built this way ensures that documents pass Logo's own validations.

• Pros: Records are created in line with Logo's business rules, behavior is more predictable across version updates, and it is the method accepted on the support side.
• Cons: Availability depends on product, version and license; some services may require an additional module or license. You need to confirm with your Logo business partner which interfaces are available in your installation.

The database layer#

Logo products store their data in an SQL database. Connecting directly to the database for read purposes (for example, pulling stock and prices) is technically possible.

• Pros: Fast, and practical for reporting and reading.
• Cons: Writing directly to the database bypasses Logo's business rules; it can cause inconsistencies in balances, costs or related tables, and the table structure may change with a version update. It is therefore not recommended for writes; even for reads, it should be done only with a read-only user.

Ready-made connectors#

There are off-the-shelf integration products on the market that connect Logo with common e-commerce platforms and marketplaces.

• Pros: Quick to set up, common scenarios are ready, and maintenance is the vendor's responsibility.
• Cons: If your workflow is non-standard (custom pricing rules, complex variant structures, different warehouse logic), flexibility may be limited. Subscription costs and the fact that data passes through a third party's servers should also be considered.

Custom middleware#

A separate middleware layer that runs on your rules is placed between Logo and the e-commerce system. This layer receives orders, transforms them, saves them through Logo's official interfaces and logs every step.

• Pros: Fits your workflow exactly, manages multiple channels from one place, and error handling and reporting can be designed the way you want.
• Cons: Requires ownership of development and maintenance. If you have few channels and a standard process, it can be heavier than needed compared with a ready-made solution.

In practice these methods are often combined: database views for reads, official interfaces for writes, and a ready-made connector or custom layer for the channel connection.

How it relates to the e-Invoice and e-Archive flow#

In Turkey, invoices for online sales are issued either as e-Invoices or e-Archive invoices depending on the buyer. If the buyer is registered for e-Invoice, an e-Invoice is issued; otherwise it's usually an e-Archive invoice. On the Logo side, these documents are typically created and sent through Logo's own e-transformation solutions or the private integrator you work with.

The integration's job here is to make sure the invoice is created with the right data: the right customer account, the right tax number or national ID, the right VAT rate and discount. Once the invoice is created, writing the invoice number or document link back to the e-commerce side lets the customer see their invoice on the order page. Most marketplaces also expect the invoice to be uploaded. Because regulatory details can change, we recommend reviewing e-document rules together with your accountant.

Sync frequency and conflict handling#

Not every type of data needs to be synchronized at the same frequency.

• Stock: Updated every few minutes depending on your sales velocity, or triggered on change. With fast-moving products, delays lead to selling items you don't have.
• Prices: Usually on change or a few times a day is enough.
• Orders: Pulled at short intervals, or in real time through notifications (webhooks) from the e-commerce side.
• Payments: Daily or more often, depending on what the bank and payment provider offer.

A conflict occurs when the same data changes differently on both sides. The most robust rule is to define a single source of truth for each type of data: Logo for stock and prices, the e-commerce side for orders. That way the question "which one is right?" doesn't have to be debated every time. Keeping a safety margin, that is, closing the last few units of critical products to sale, also reduces overselling caused by sync delays.

Error logging and monitoring#

When an integration works, it's invisible; when something goes wrong, it's often noticed days later. To prevent this:

• For every transferred record, store the source number, the document number in Logo, the time and the result.
• Failed records should not be silently skipped; they should land in an error list with the reason and be retryable.
• Notify the responsible person when no orders arrive for a certain period or when the error count rises.
• To prevent the same order from being processed twice, store each order's external reference in Logo and check it before every transfer.

Setup steps#

A Logo integration project generally follows these steps:

1. Analysis: Which channels are there, how many orders arrive per day, which Logo product and version is in use, which interfaces are available, how does invoicing work? At this stage, the manual work is written down step by step.
2. Mapping table: Product codes, variants, shipping and payment methods, VAT rates and warehouse codes on the e-commerce side are matched one by one with their counterparts in Logo. It's the least visible but most decisive step of the project.
3. Test environment: The integration is tried on a copy of the live company or a test company. Scenarios such as a normal order, cancellation, return, partial shipment, a discounted product and a basket with mixed VAT rates are run separately.
4. Go-live: The switch is planned for a period of low order volume. In the first days, automatically created records are checked by hand; if needed, only one channel is opened for a while.
5. Monitoring: The error list, transfer times and stock differences are reviewed regularly. After version updates on the Logo or e-commerce side, the core scenarios are tested again.

Common mistakes#

• Leaving product code mapping until last: If the stock code on the site differs from the item code in Logo, or variants aren't defined as separate cards in Logo, the integration posts the wrong product. Mapping should be finished before technical development.
• Overlooking VAT and discount differences: Prices on the e-commerce side are usually VAT-inclusive, while Logo may hold them VAT-exclusive. If it isn't clear how basket discounts, coupons and shipping fees are spread across lines, small rounding differences appear between the invoice total and the amount collected.
• Duplicate records: Retrying after a network outage or timeout can create the same order twice. That's why a duplicate check on the external order number is essential.
• Opening a new customer account for every order: You quickly end up with an unmanageable account list. The account policy should be decided at the start.
• Ignoring returns and cancellations: An integration that only covers successful orders requires manual fixes when a return comes in and throws stock off.
• Writing directly to the database: It looks like a shortcut, but because it bypasses Logo's business rules it leaves inconsistencies that are hard to fix later.

Where to start?#

The best starting point is to list the work that is done by hand today and write down the time spent on each item. In most businesses, order transfer and stock updates are at the top of that list. Getting these two flows solid first, then moving on to payment and bank matching, reduces risk. We describe our general approach to evaluating processes for automation in our guide to AI and automation in Bursa.

If you need an integration between Logo and your online store or marketplace shops, you can reach us through our contact page to review your current process together. You can explore our other solutions on our services page.

Frequently Asked Questions#

Which Logo product do I need for a Logo integration?#

Integration is possible with different products such as Logo Tiger, Logo Go and j-Platform, but which interfaces are available depends on the product, version and license. Before you start, confirm with your Logo business partner which services are enabled in your installation.

Is a ready-made connector or custom development the better choice?#

If you have few channels and your product structure and workflow are standard, a ready-made connector is usually faster and more economical. If you need custom pricing rules, complex variant or warehouse structures, or to manage several channels from one place, a custom middleware layer is more flexible.

How often should stock be updated?#

It depends on your sales velocity. For fast-moving products, intervals of a few minutes or updates triggered on change are preferred. For slow-moving products, less frequent updates may be enough. Keeping safety stock on critical products reduces the risk of overselling.

Does the integration also issue e-Invoices and e-Archive invoices?#

The integration ensures the invoice is created in Logo with the right data; sending it as an e-Invoice or e-Archive invoice usually runs through Logo's e-transformation solution or your private integrator. The whole flow can be connected end to end, but we recommend reviewing e-document rules with your accountant.

Is Logo bank integration different from e-commerce integration?#

They serve different purposes. E-commerce integration manages the flow of stock, prices and orders; bank integration imports bank transactions into Logo and matches payments with the relevant customer accounts and orders. When both are in place, the process from order to payment becomes traceable end to end.

How do we prevent the same order from being transferred twice?#

Each order's number on the e-commerce side is stored with the record in Logo, and before every transfer the system checks whether that number has already been processed. When retries after an error go through the same check, duplicate records don't occur.