SAML vs OIDC: How the Two SSO Protocols Differ and Which to Use for Each App
SAML vs OIDC explained: XML-based SAML and JSON/JWT-based OpenID Connect compared across web, mobile and API use cases, with a six-step way to choose.
9 min read
System Integrations (API)
Enter Data Once, Use It Everywhere
System integration connects separate software, such as ERP, CRM, web shop, payment gateway, e-invoicing, courier and SMS services, through their APIs so data moves between them on its own. An order is entered once; stock, the invoice and the shipment are created in the other systems automatically. We connect what you already use and log every transfer.
Accounts live in one package, sales in another, the web shop and courier portal in separate browser tabs. An order is taken in one place, invoiced in another and deducted from stock in a third, with staff re-keying the data in between. It costs hours, the figures drift apart, and by month-end nobody is sure which screen is right.
Once the systems are integrated, that re-keying disappears: when an order is placed, stock is reduced, the invoice is issued, a shipment is booked and the customer receives tracking details. We build the links to keep a log of every transfer, so when one fails you can see which record is stuck and the right person is alerted.
For international companies operating in Turkey, this is often where local requirements bite: GİB e-invoicing, Turkish banks' virtual POS systems and local ERPs such as Logo and Mikro need to talk to your group systems. We handle both sides.
System Integration Scope: What We Connect
ERP:
Two-way transfer of sales, stock, customer account and accounting data with Logo, Mikro, Netsis, SAP and bespoke ERPs.
CRM & HR:
Customer records, order history and call logs into Salesforce, HubSpot or your own CRM; staff data kept in step with HR and payroll software.
Payments:
Card collection through iyzico and Turkish banks' virtual POS services, with the payment result posted to the order and customer account automatically.
e-Invoice / e-Archive:
Invoices created and sent through GİB-approved integrators, so a completed sale produces its invoice without anyone typing it.
Couriers & Logistics:
Shipments booked and tracking numbers retrieved through carrier APIs such as Aras, Yurtiçi, MNG and UPS, with tracking details sent to the customer.
SMS & Email:
Order, appointment and payment notifications through SMS providers such as Netgsm and Twilio, and through email platforms.
Maps & Location:
Address validation, route planning and field team locations via Google Maps and similar services.
Bespoke & Legacy Systems:
Including older or poorly documented software: REST, SOAP, GraphQL, file exchange or direct database links, whichever the system allows.
Two Ways to Work With Us
Every integration starts with a data map: where each piece of information originates, where it needs to go, and which system is the master for each field. Scope, phases and cost are then set out in a written proposal. From there, one of two routes applies:
Connecting Your Existing Software
It does not matter whether we or another vendor supplied it. If it offers API access, we connect it to the rest of your systems and your teams keep working in the screens they know.
New Software, Integration Built In
Software we build for you is designed with its connection points from day one, so adding a new bank, carrier or marketplace later does not mean reworking the system.
See also API Integration for API development on the software side, and Integrated Systems for bringing several modules under one roof.
Questions we hear most often
Frequently Asked Questions
What is system integration?
System integration connects separate software, such as ERP, CRM, web shop, payment gateway, e-invoicing, courier and SMS services, through their APIs so data moves between them on its own. An order is entered once; stock is reduced, the invoice is issued, the shipment is booked and the customer receives tracking details, with no re-keying.
Which systems do you integrate?
Logo, Mikro, Netsis, SAP and bespoke ERPs; Salesforce, HubSpot or your own CRM; HR and payroll software; iyzico and Turkish banks' virtual POS services; e-invoice and e-archive through GİB-approved integrators; carriers such as Aras, Yurtiçi, MNG and UPS; SMS providers such as Netgsm and Twilio; and map services such as Google Maps.
Can you connect our group systems to Turkish e-invoicing and local ERPs?
Yes. For international companies operating in Turkey, GİB e-invoicing, Turkish banks' virtual POS systems and local ERPs such as Logo and Mikro often need to exchange data with group systems. We handle both sides of that connection, starting from a data map that sets which system is the master for each field.
Do we need to replace our software to integrate it?
Usually not. Whether we or another vendor supplied it, if the software offers API access we connect it to the rest of your systems and your teams keep working in the screens they know. For older or poorly documented software we look for another route: REST, SOAP, GraphQL, file exchange or a direct database link.
What happens when an integration fails?
Every link is built to log each transfer. When one fails, you can see which record is stuck and the right person is alerted. Problems are therefore spotted when they happen rather than at month-end when the figures no longer match, and you can trace when each record was transferred.
How does an integration project start?
Every integration starts with a data map: where each piece of information originates, where it needs to go and which system is the master for each field. Scope, phases and cost are then set out in a written proposal, and you choose between connecting your existing software or new software built with integration in from day one.
Have a different question? Ask Us