What are Logo's products and who uses them?
Logo Yazılım is one of Türkiye's long-established business software vendors; together with Netsis, its ERP systems are the ones most widely used in Türkiye. Logo Go, common among small and mid-sized businesses, Logo Tiger for broader needs, and j-Platform for large organizations are ERP solutions from the same brand at different scales. Accounting, stock, purchasing, sales, production and finance all run in these systems.
Whichever Logo product you use, the question is the same: how does the information in Logo reach your e-commerce site, your dealers and your management reports safely? A Logo integration answers that question.
What do we connect with Logo?
| Data | Direction | Frequency |
|---|---|---|
| Item card, variant, unit | Logo → site / portal | On change |
| Stock quantity (per warehouse) | Logo → site, portal, marketplace | At short intervals |
| Sales price, dealer price list | Logo → site / portal | On change |
| Order | Site / portal → Logo | Instantly |
| New customer account | Site / portal → Logo | Together with the order |
| Account balance, open items | Logo → B2B portal | Several times a day |
| Invoice and delivery note details | Logo → site / portal | When the document is created |
| Shipment tracking number | Carrier → site, Logo | When the shipment is created |
Flows that write orders, accounts or vouchers into Logo fall under the integration service and are set up with a user that has limited permissions. We explain how those decisions are made on the ERP integration page.
No need to write to Logo for reports: READERP
What many companies really need is "accurate, fast reports from Logo". READERP connects to Netsis, Logo and the other common ERP and finance platforms on the market with read-only access; it never writes a single line to Logo. It is installed the same day and merges fiscal-period databases split across years into a single time series. Cash, Receivables, Revenue, Stock, Payroll, Cash cycle and Confirmation reports come ready; you type your question in Turkish, and custom financial reports are added when needed.
Typical scenarios
- Dealer ordering portal: A dealer sees their own prices, stock from Logo and their balance in the portal and places an order. The order lands in Logo; after shipment, the invoice details flow back to the portal. This is what a B2B dealer portal does in practice.
- Multichannel sales: Product data goes from Logo to IMFLEXI or your current site and to the marketplaces; whichever channel a sale comes from, stock is managed in one place.
- Management meeting: Instead of preparing receivables aging and revenue breakdowns by hand every week, the finance manager opens them in READERP; Logo is not touched.
How do we work?
- Analysis: We learn your Logo product, version, company and period structure and where the server lives. If you have a Logo solution partner, we work in coordination with them.
- Mapping: Item codes, warehouses, unit sets, VAT and discount rules and account matching criteria are put in writing.
- Test environment: The flow is tried on a test company or a copy of the database.
- Go-live: Flows are switched on gradually, and we check the outputs together in the first days.
- Monitoring: Every transfer is logged. A failed record goes into an error queue and is retried automatically; if it still fails, an alert goes out and the cause can be read from the log.
What to prepare before we start
To make the first call productive, having the following information ready is enough; we fill in any gaps together:
- The Logo product you use (Go, Tiger or j-Platform) and its version
- The server Logo runs on: in-house or in a data center?
- Your company and period structure; do you use more than one company card?
- Contact details of your Logo solution partner
- Product groups and warehouses to be opened to the site or portal
- A list of transfers done by hand today and a rough daily order count
This list makes clear which flow comes first and how long it will take. The written proposal is prepared based on this information.
Security and KVKK
The integration user can access only the fields it needs; reporting is fully read-only. Database and service credentials are kept in a restricted configuration, not in the code. For the personal data in account cards, we limit the transferred fields to what is necessary and meet the requirements of KVKK (Türkiye's Personal Data Protection Law) in full, at no extra charge. The flow stays between servers in Türkiye.
Related Globya solutions
- Integration service
- Netsis integration
- Recommended reading: ERP and e-commerce integration
To talk about your Logo setup, call +90 850 432 55 13 or use the contact page. Pricing follows a written proposal after the discovery call. Describe your needs now in 3 minutes
Frequently asked questions
Is the same integration used for Logo Go, Tiger and j-Platform?
The logic is the same, but the connection method is chosen according to the product and version. In the initial analysis we determine which route is safest.
Is it a problem that we work with a Logo solution partner?
Not at all. We coordinate with your solution partner on settings and permissions on the Logo side, while responsibility for the integration stays with us.
We only want reports. Do we need to give write access to Logo?
No. READERP works read-only and never writes any record to Logo.
Does the integration stop when we move to a new fiscal period?
We plan the period change in advance; the integration is pointed to the new period, and data from the old period is kept for reporting.