Integrations
Our integrations service connects your accounting, e-invoicing, shipping, payment and bank systems. Data flows from one system to the next without anyone retyping it. A project usually takes 2–6 weeks.
Who are integrations for?
Integrations are for companies that type the same data into more than one system. Typical clients copy orders from their website into accounting, prepare shipping labels one by one, or match bank transactions by hand. That takes time and creates errors.
Which systems do we connect?
Most often accounting software, e-invoice providers, shipping companies, payment providers and banks. Your online store, CRM or custom software can sit at the centre. The other system needs to offer an API, a door through which two programs exchange data. Where a system can send a message when something happens, we use a webhook.
The most common connections have their own guides: accounting and ERP integration, marketplace integration and payment gateway integration.
What do we do?
First we write down which data moves, in which direction and how often. That list becomes the definition of done. Then we build the connection with error handling. If the other system does not respond, the transfer is queued and retried, not lost.
What is included
-
Data flow plan
What goes where and when is written down. The definition of done follows this plan.
-
Building the connection
We work with the other system's API or file exchange.
-
Retries
Failed transfers are queued and retried, not lost.
-
Alerts
If a transfer fails, the right person gets an email or notification.
-
Logs
See which record was sent, when, and with what result.
How the project runs
- 01 You write, we reply within a business day Day 0 you list the systems you use. Day 1 we reply. Day 2 we talk for 30 minutes about the data flow.
- 02 One-page quote and definition of done Day 4 you get the quote. Day 5 the definition of done is signed, with each connection as its own item.
- 03 Build We build against the other systems' test accounts. If there is no test account, we say so up front.
- 04 Testing We test real cases: cancellations, returns, missing data and a system that does not answer.
- 05 Go live and handover We go live on the promised date, watch the first days closely and hand over notes and logins.
What if the other system changes?
When another system changes its rules, the integration needs an update. We fix bugs for free for 30 days after launch. After that, monthly maintenance and support keeps connections current, and it is optional. The code is in your repository. If you want to leave, one email is enough.
Frequently asked questions
How long does an integration take?
Usually 2–6 weeks, depending on the number of systems and the quality of their documentation.
Can you connect to the software we use?
If it offers an API or file exchange, usually yes. We check together on the first call.
Is data lost if the connection drops?
No. Transfers are queued and retried, and failures trigger an alert.
Which e-invoice provider do you use?
Yours. You choose the provider, and we use the connection it offers.
Will the integration change our existing website or software?
Usually not. The connection sits between your existing systems. If a small setting is needed on your site or software, we say so up front and write it into the definition of done.
How do we decide which system to connect first?
We start with the connection that creates the most manual work. That is usually orders to accounting, or orders to shipping. We set the order together on the first call.
What changes the price of an integration?
The number of systems, the direction and frequency of the data, and the quality of the other system's documentation. Systems with no test account or thin documentation take longer. Each connection is its own line on the quote.
Can a marketplace, our store and accounting be connected at once?
Yes. Orders come in from the marketplace, stock syncs with the store, invoices go out through your provider and records land in accounting. We write the flow step by step, with each connection as its own item in the definition of done.
Who owns the integration code?
You do. The code is in your repository from day one and runs on a server in your account. We hand over integration notes so another team can maintain it too.
Do you work with companies outside İzmir?
Yes. Integration work runs fully remote. We work with clients across Turkey and abroad by phone and video.