01
Number of systems to connect
Each new system means its own documentation, test environment and mapping.
Web Software
Integrations
We connect your site with your payment provider, shipping carrier, e-invoicing provider, accounting/ERP software and marketplaces. No more entering the same data on several screens by hand: orders, stock and invoices move in a single flow.
Live demo · failure scenarios
What happens when the other system doesn't answer?
An integration proves itself when things go wrong, not when everything works. Try an outage on the shipping API, or the same notification arriving twice.
↳ Pick an outage type, optionally turn on duplicate delivery, then play.
Illustrative flow; retry count and delays are tuned per project.
How we prepare before integrating
Before any code is written, it must be clear what each system sends to the other and which one is the reference. The analysis stage consists of these five steps.
Let's talk about your project
Book a call ↗We list all the software you use and every manual data entry step.
API documentation, test environments and access keys for each system are obtained under your account.
A field mapping table is prepared: product code, VAT rate, customer account, warehouse, order statuses.
The connection is built in a test environment first; scenarios with faulty and missing data are tried.
In production, every transfer is logged and alerts are set up for failed operations.
Scope
Systems we can connect
Payment systems
iyzico, PayTR and bank virtual POS; 3D Secure, installments, refunds. No order is confirmed until the payment result is verified via callback.
Shipping carriers
Shipment creation, label printing, tracking numbers and delivery status queries with Yurtiçi, Aras, MNG and similar carriers.
e-Fatura and e-Arşiv
Order-linked invoicing under Turkey's e-invoicing system through your e-invoicing provider or accounting software, with the invoice PDF sent to the customer.
ERP and accounting
Customer account, stock, price and order transfer with software such as Paraşüt, Logo and Mikro. Can be set up one-way or two-way.
Marketplaces
Product, stock, price and order sync with Trendyol and Hepsiburada; marketplace orders collected in a single panel.
SMS and email
Automatic order, shipping and appointment notifications through your SMS provider or email service.
CRM and form flows
Inquiries from web forms and ads saved as records in your CRM and assigned to the sales team.
Product feeds
Product feeds for Google Merchant Center and Meta catalogs, updated as prices and stock change.
Custom APIs and middleware
REST/webhook connections for any system with an API; where there's no API, CSV/XML file transfer or scheduled data sync.
Integration types
The connections we build most often and what they do behind the scenes
Your site
01 / 05
Payments: iyzico, PayTR, virtual POS
Payment confirmation comes back from the payment provider as a callback; the order is marked "paid" only after this verification. 3D Secure, installment tables, full and partial refunds are all part of this connection. Card data never passes through your server; the payment form runs on the provider's infrastructure.
When: When the customer reaches the payment step
Data that flows
- Payment form (on the provider's side, 3D Secure)outbound
- Payment approval — verified via callbackinbound
- Full and partial refundsoutbound
Request a Quote ↗
List the software you use and we'll look at it together.
Technical approachWhat a solid integration
What a solid integration
needs to have
Most integrations work on day one; problems show up when the other system doesn't respond, a product code changes or the same order arrives twice. That's why we apply the following in every project.
integration / source-of-truthexample
SiteERP
Stockcopysource
Pricecopysource
Orderssourcecopy
Accountscopysource
The source of truth is defined up front
Is stock kept in the ERP or on the site? Who changes prices? An integration written before these questions are answered leads to two systems overwriting each other's data. We designate a single source of truth for each type of data and document it.
— Example flow
What happens behind the scenes when an order comes in?
Without integration, each of these four steps is done by hand on a separate screen.
- 01 · Payment
The payment provider approves the payment and the order is marked "paid".
- 02 · Stock
Stock drops on the site and on marketplaces at the same time.
- 03 · Invoice
An e-Arşiv invoice is issued and the customer account is transferred to the accounting software.
- 04 · Shipping
A shipment is created and the tracking number goes to the customer.
Process
How an integration project progresses
Preparation
What we'll need from you before we start
The sooner this information arrives, the shorter the analysis. We'll fill in any gaps together.
0/12
items ready
Tick what you already have; ticks stay on this screen only and aren't sent anywhere.
~/preparation/accounts-and-access
Budget
What determines price and timeline
02
Direction of data flow
Just sending orders is one-way; pulling stock and prices back is two-way work that requires conflict rules.
03
Quality of the other system's API
Work moves quickly with well-documented services that have a test environment. With undocumented or installed (on-premise) software, discovery takes longer.
ACME LtdAcme Ltd.ACME LTD
04
Data cleanliness
If stock codes are inconsistent or the same customer is recorded several times, the data needs cleaning up before integration.
webhookscheduled
05
Sync frequency
Real-time (webhook) sync and hourly/daily scheduled sync need different infrastructure.
06
Existing platform
On hosted-package sites we work within the limits the package allows; custom software requires access to the source code.
After the analysis, each connection is quoted as a separate item, so you decide which one to start with.
Related services
Work often requested alongside integrations
FAQFrequently Asked
Frequently Asked
Questions
What matters is what the other system allows. Services such as iyzico, PayTR, the shipping carriers, Trendyol, Hepsiburada and Paraşüt have public APIs. With installed software such as Logo and Mikro, the connection is usually made through the program's own web service or middleware provided by your reseller. For systems without an API, options such as file transfer (CSV/XML) or database-level reads are considered.
In most cases, yes. We first review your current site's platform (WordPress/WooCommerce, a hosted package or custom code). With hosted packages, the app/plugin structure the package allows sets the limits; with custom software, we need access to the source code.
Yours. Payment provider, carrier, marketplace and e-invoicing accounts are opened in your company's name; we only use the keys needed for development. At the end of the project, you receive a list of the keys and where each is configured.
A single payment or shipping connection and two-way stock and price sync with an ERP are not the same scale of work. The timeline depends most on the quality of the other system's documentation, whether it has a test environment and how clear the field mapping is. After the analysis, the proposal includes a stage-by-stage estimate.
We build integrations to prevent data loss. Every transfer is logged; if the other system doesn't respond, the operation waits in a queue and is retried. Each record is matched with a unique ID so the same order isn't transferred twice. Email alerts are set up for recurring errors.
Only the fields the job requires are transferred between systems. Connections run over HTTPS, and access keys are kept in server environment variables, not in the code. Together we assess whether a new data transfer needs to be reflected in your KVKK (Turkey's Personal Data Protection Law) privacy notice and data processing inventory.
Payment, shipping and marketplace companies update their APIs periodically and retire old versions. For projects with a maintenance agreement, we follow these announcements and make the necessary updates; without one, the update is quoted as a separate job.