GAZIANTEP · SOFTWARE INTEGRATION

Gaziantep integration software that never makes you enter the same data twice in a day

E-invoice (e-Fatura) and e-dispatch (e-İrsaliye), marketplace orders, couriers, bank statements, ERP to ERP, weighbridge and machine data. We do not replace your programs; we build the middleware layer that closes the gaps between them. We go out to factories in the Başpınar organised industrial zone (OSB) and Şehitkamil and look on site, because integration work usually gets stuck not on the screen but in the field: in the weighbridge cable, in the warehouse's wireless coverage, in the single computer in accounting.

Free discovery call +90 543 930 12 72

The picture in Gaziantep

In most companies in Başpınar OSB and Şehitkamil, the accounting side is settled on Logo, Mikro or Netsis. The disconnect is not in that backbone; it lives between it and the marketplaces, couriers, truck weighbridge, production tracking program and dealer orders. Rolls and metreage in carpets, truck weighing in flour and pulses, batch and pallet in packaging — each is born on a separate piece of paper and typed into the system in the evening.
In our own field research we surveyed 1,108 companies registered in the Gaziantep OSB. We flagged 294 of them as verified exporters — roughly a quarter. For an exporting company the integration load doubles: the domestic e-document regime on one side, and overseas orders, customs paperwork and foreign-currency flows on the other. The same order is rewritten in two separate systems in two separate formats.
The same research showed that roughly half of the companies have a website. As order channels multiply, the work does not get easier — it fragments: one order arrives from a marketplace, one from the company's own site, one from a dealer by phone, one from an export customer by e-mail. In an estimated sub-breakdown of the same data set we tagged 45 companies on the flour and milling side and 41 in packaging; this labelling is not a definitive classification, but in these two groups it shows that the subject of integration is not the office software but the weighbridge and the label out on the floor.
On the e-document side, the mandatory scope has been widening step by step over the years; a company outside the scope today can fall inside it tomorrow. The binding answer on which scope you fall under comes from your financial advisor — we are not tax advisers. Our job is making sure the software side is ready when your turn comes; done before the squeeze, this preparation is a calm installation, and done after it, an emergency.
We are in this city too. Questions like the weighbridge's serial port, the handheld terminal's coverage in the warehouse or the age of the single computer in accounting are not settled over the phone; you have to take your tools, go, look and measure. Visiting the factory is not a separate line item for us — it is a normal part of the job.

When the same information is typed in two or three times a day

Marketplace orders are read off the screen and typed into the accounting program by hand. On busy evenings one gets skipped or a quantity is mistyped — and the error surfaces at loading time, the most painful moment to fix it.
Stock is kept in two places: the real quantity in the warehouse and the quantity shown on the marketplace. As the two drift apart, goods you do not have get sold, bringing cancellations and seller-rating penalties.
Courier tracking numbers are copied one by one and sent to customers. How many parcels actually went out that day only becomes clear by comparing against the courier company's list.
The bank statement is downloaded as a PDF at month-end and matched to customer accounts by hand. Working out which payment belongs to which invoice becomes a long reconciliation exercise, and in the meantime nobody knows the real balance.
The invoice is entered first into your own program, then into the e-invoice portal. When the two do not match, finding the source of the error takes longer than issuing the invoice from scratch.
The weighbridge ticket stays on paper. The truck's tare, gross and net values are copied from the operator's notebook into the system in the evening; when a customer disputes a delivery, your only evidence is a faded slip.
The production tracking program and the accounting ERP know the same product by different codes. Every month someone sits down to match the two lists, and that job is nobody's actual role.
The proforma, weight list and customs paperwork for an export customer are each prepared by hand. Because the same order's lines are written three times into three files, changing one line means re-checking all of them.
The decision to open a new marketplace or add a second courier is postponed not on commercial grounds but over the question of who will do the data entry.
When the employee who handles all this leaves, nobody knows what they actually did — because the integration was never software; it was that person's daily routine, kept in their head.

We put a bridge between the two systems, not a person

What we call integration is a middleware layer that moves data from one system to the other with no human touch and with validation. We do not try to replace your existing programs; we close the gap between them. Which data flows in which direction, how often, and what happens on error is put in writing at the start. That way the bridge becomes an asset that can be handed over — unlike a routine living in one person's head.

e-Invoice, e-dispatch and e-ledger bridge

We build a direct connection between your own program and your special integrator (an intermediary authorised by the Turkish Revenue Administration). The invoice is created in one place, with no second manual entry into the portal; incoming invoices land automatically too. Your financial advisor tells you when you fall within the mandatory scope; we make sure the connection is built before that date, tested with real data and reconciled. We work at the same table as your financial advisor.

Marketplace and e-commerce synchronisation

Two-way flow of stock, price, order and returns data with Trendyol, Hepsiburada and your own web store. The real stock in the warehouse and the stock in the shop window become the same number; orders land in accounting by themselves. In variant-heavy products such as carpets, home textiles and food, matching the size, colour, pattern and weight matrix is the hard part — and that is where we do the real work.

Couriers, dispatch and export paperwork

When an order is confirmed, the shipment is opened in the courier's system, the barcode is printed and the tracking number is written into the customer notification by itself. The delivered status flows back and matches against collections. On the export side, the proforma, weight list and packing list are generated from the same order record; the job of correcting three files whenever one line changes disappears.

Bank, collections and account reconciliation

Bank account movements flow into the system automatically and are matched against customer accounts. With matching rules built on description, amount and date, part of the month-end manual matching is done by the rules; unmatched items are collected in a separate list, so nothing gets lost. Cheque and promissory-note tracking can join the same flow.

Data bridges between ERPs, and between ERP and production

Product code, customer account, stock and order mapping between your accounting ERP and a production tracking program, dealer portal or a group company's separate system. The production layer we built to write alongside Netsis without touching it belongs to this family: the backbone stays in place and data flows cleanly in both directions.

Weighbridge, terminal and machine data

Weighing data from the weighbridge, barcodes read on handheld terminals and counter values from machines written straight into the system. In a project where we built a weighing and labelling station, we ran the scale and the label printer in a single flow; the logic here is the same. The paper slip is replaced by a timestamped record you can go back and check.

How we run an integration project

01
Half a day at the factory
We come to Başpınar or Şehitkamil, sit next to the person who carries the data by hand, and watch the screen and the notebook together. Which information travels from where to where, who enters what and when, what happens when an error appears — the answer to that lives at that desk, not in the meeting room. If there is a weighbridge we go and stand at it; if there are terminals we go into the warehouse. This visit is free of charge, and at the end of it we tell you plainly whether the job is feasible.
02
Data map and reconciliation rules
We put in writing which field maps to which, which side is treated as the source of truth for each piece of information, and which rule applies when there is a conflict. This document matters more than the code itself; most integrations break not for technical reasons but because this rule was left vague.
03
A pilot with a single flow
We do not connect everything at once. We pick the single flow that creates the most manual work, build it end to end and run it with real data. We do not move to a second flow until the pilot produces correct results; that keeps both risk and budget under control.
04
Parallel running and go-live
The new bridge runs alongside the old method for a while. For the same day, the result the system produces is compared with the result produced by hand; the old method is not switched off until the two start to agree. The way back is always kept open.
05
Monitoring and incident duty
A bridge is not something you build once and abandon: the other side changes its interface, the internet drops, a record gets rejected. We monitor the flow, raise an alert when there is an error, and write into the contract who intervenes and when. An unmonitored integration is noticed on the day it silently stops.

Frequently asked questions

When will mandatory e-invoicing and e-ledger apply to us?

The binding answer comes from your financial advisor; we are not tax advisers and we will not commit you to a date. The scope widens gradually over the years by revenue threshold and line of business, so being outside it today is not a permanent state. Our job is making sure the software side is ready when your turn comes: the special integrator connection built, tested with real data and reconciled. Doing this preparation early is both calmer and cheaper than doing it against a deadline.

Do we need to replace our current ERP?

No — quite the opposite. Our job is to protect your backbone. Whether it is Logo, Mikro, Netsis or a program written specifically for the company years ago, we build a layer that talks to it through its database or interfaces without touching it. An ERP replacement is both expensive and risky; in most cases integration makes that decision unnecessary.

The marketplaces have their own integrator firms. What's different about you?

Off-the-shelf integrators handle the standard scenario and are enough for most companies. Where you hit the limit is usually this: your variant structure is non-standard, your pricing varies by dealer and customer, the stock coming from production is not real-time, or your ERP is not on that integrator's supported list. We start where the ready-made product ends; where it makes sense, we keep the ready-made integrator in the flow and write only the missing piece.

What happens if the other side goes down while the integration is running?

That is a normal condition the design must expect. A record that cannot be sent is not lost; it waits in a queue and is retried when the other side comes back. So that a retry never processes the same record twice, we mark every transaction with a unique key. If it still fails after a set number of attempts, the system does not stay silent — an alert goes to the responsible person.

Is it really possible to capture data from weighbridges and machines?

In most cases yes, but we will not promise without seeing the device. Weighbridges that output data over a serial port or the network connect directly. For older devices with no output, we either place a reader in between or set up a one-tap entry screen for the operator; both replace the slip written on paper. We give the answer by looking on site, not from a catalogue; for a weighbridge, coming to the OSB to check the device's make, model and output is half an hour's work.

We export. Can the international side be connected too?

It can, but you have to look at what the other side provides. If your customer uses a supplier portal, orders can be pulled from it; if orders arrive as a standard file attached to an e-mail, that file can be read and written into the system; if there is neither, we at least make sure the proforma, weight list and packing list are generated from the same record. The pattern we often see among exporters in Gaziantep is the same order being written twice, in two separate regimes, for domestic and international — that is usually the first target of the integration.

How long does it take, and what does it cost?

We do not quote a figure before the discovery visit, and we suggest treating any proposal that does with caution. Duration and cost depend on how many systems are being connected, whether the other side provides an interface, and how clean your data is. That is why we split the work into single-flow packages with scope and duration written up front; when the first package is done, you see the result and decide for yourself whether to continue.

Who keeps the source code and the accounts for the bridge you build?

All of it stays with you. Integrator, marketplace and courier accounts are opened in your name; we leave no connection running through our own users. The source code, the data mapping document and the installation notes are handed over; if another team wants to carry on, they can. Being locked into a software supplier is precisely the dependency problem you are trying to solve with integration.

Let's measure the data carried by hand, just once

Tell us which information gets typed in how many times today, and we will come to your factory and look on site. At the end of the visit we tell you plainly which flow can be rescued and which should be left untouched for now. Başpınar and Şehitkamil are a phone call away; a quotation only means something after seeing the site.

+90 543 930 12 72 Send a message