We do not replace your Logo, Mikro, Netsis or SAP accounting backbone. From trip planning to fuel tracking, from subcontractor settlements to customer shipment visibility, we take the operation that today runs on Excel and WhatsApp and move it into a single operational layer — real-time, traceable and reconciled. Not an off-the-shelf package: built for your business. Source code and data are one hundred per cent yours.
Gaziantep is an export-heavy logistics hub on the main road corridor linking the south-east to the west, running mixed fleets of owned and hired tractor units. In most firms the accounting is settled; but trip, fuel and settlement data runs outside the system. If the points below sound familiar, the issue is not replacing the ERP — it is building the right layer on top of it.
The sector's software landscape splits into layers: a horizontal accounting/ERP backbone, a sector-specific TMS, vehicle tracking-telematics, and warehouse (WMS) plus e-transformation tools. Each layer does its own job well, but the accounting-operations-telematics triangle between them stays open. Let us lay out the table as it really is, so it is clear where the solution fits.
| Layer | Software in use today | The gap it leaves |
|---|---|---|
| General accounting / bookkeeping / ERP (horizontal backbone) | Logo Tiger / GO, Logo Netsis 3, Mikro (Jump, Fly), ETA SQL, SAP Business One and S/4HANA (at large 3PLs/freight forwarders), Oracle NetSuite; local packages such as Vega and Akınsoft | A solid backbone for receivables, invoicing, cheques, banking, VAT/returns and e-Invoice/e-Archive; fixed because of GİB (Turkish Revenue Administration) obligations. But it was not designed for trip planning, trailer-tractor pairing, trip costing or TIR carnets; operations usually stay outside it. |
| Transport Management System (TMS — sector-specific) | Siber Yazılım International Road Transport Programme, KG Yazılım Lojistik, Lojiper, Select Optimus TMS, Transportlogy, Dynamics Trans, ATS PRO, Isystems, Solves logistics ERP; on the multinational side Oracle Transportation Management (OTM), SAP TM | The sector's operational brain for trip planning, load pools, booking-quotation, fleet document-maintenance, driver advances, trip costing and TIR carnet/ECMT tracking, plus U-ETDS and NCTS/T1-T2. Yet in Gaziantep many SMEs still use Excel instead; and where a TMS is installed, it is rarely fully integrated with accounting and telematics. |
| Vehicle tracking / telematics / fleet (GPS, CANbus, fuel) | Arvento (market leader), Mobiliz, Triomobil, Seyirmobil, TNB Mobil, Fora Mobil; operator packages: Turkcell, Vodafone Business Vehicle Tracking, Türk Telekom Vehicle Tracking | Strong for live location, route history, speeding/harsh braking and driver behaviour scores, plus CANbus fuel consumption, RPM, fault codes and cold-chain temperature sensors. Effective at cutting fuel costs; but in most firms it is not integrated with the TMS or accounting and is watched in a separate portal. |
| Warehouse Management System (WMS) and bonded warehouses | Netadam WMS, Mecalux Easy WMS, SAP EWM/WMS, Hamurlabs WMS, inksen, TreyLog; local solutions with bonded-warehouse/customs integration | Functional for goods receipt, put-away, picking, dispatch, RF handheld terminals and real-time stock by barcode, plus bonded-warehouse entry-exit and commission tracking. Present at 3PLs and bonded-warehouse operators; usually absent at pure-haulage SMEs, and left unconnected to the trip side. |
| e-Transformation / documents and compliance | Logo e-Çözümler, Sovos, Uni-Dox (Univera), SuareSoft, Egebilgi and other GİB special integrators; e-Delivery note, e-Invoice, e-Archive | Works integrated with the ERP for converting dispatch notes into e-Delivery notes (mandatory in logistics), e-Invoice and e-Archive. But when the field and the ERP are disconnected, delivery note data never flows into the operations system; duplicate entry and compliance errors are born here. |
| Field / manual tools (shadow IT) | Microsoft Excel / Google Sheets (trip, fuel, km and settlement tables), WhatsApp (driver-office communication), paper delivery notes/receipts, the telephone | In many Gaziantep SME hauliers the real operation runs here: trip costs, subcontractor settlements and fuel receipts live in Excel; data is collected through driver declarations and WhatsApp photos. The most widespread yet most error-prone and least transparent layer; this is the gap custom software actually fills. |
Our solution is not a rival to your existing software; it is the operational layer that fills the gap between them. Your accounting ERP stays as the finance backbone; we connect trips, fuel, subcontractors, document compliance and customer visibility to it and to your vehicle tracking. We start with an on-site discovery, then build only the modules you genuinely need.
A two-way synchronisation bridge between Logo, Mikro, Netsis or SAP accounting and your TMS and vehicle tracking (Arvento, Mobiliz). Trip, account and fuel data match automatically; keying the same trip into 2-3 places and reconciliation delays end.
A BI engine that combines telematics km and fuel + HGS tolls + driver advances + depreciation, insurance and overhead shares to produce real-time profitability per trip and vehicle, plus lane-metre calculations. Where the money is being lost is finally visible.
A module that compares CANbus consumption data with pump, receipt and fuel-company data, raises deviation alarms and flags irregular purchases. Fuel spend moves from driver declarations to measurable fact.
A mobile app for drivers that collects delivery notes, CMR and delivery photos, expense receipts and proof of delivery (POD/e-signature), and works offline too. It replaces WhatsApp and paper; the record is created where the work happens.
A web/mobile portal where customers track their own loads with live location, ETA and documents (CMR, e-Delivery note, POD). It cuts 'where is my load' calls, lowers the call-centre load and becomes a competitive edge.
Automatic alerts and missing-declaration blocking for TIR carnet and ECMT (UBAK) logbook stock-usage-returns, U-ETDS and NCTS declarations, vehicle inspection-insurance and driver SRC/licence/psychotechnical expiry dates. Penalty and unplanned-breakdown risk drops.
Not every firm needs all of them. After discovery we start where it hurts most and grow module by module. All of the systems below are built to work integrated with your existing ERP backbone and your vehicle tracking portal.
Two-way synchronisation of trip, account, fuel and invoice data between Logo/Mikro/Netsis/SAP and your TMS and Arvento/Mobiliz. Duplicate entry and reconciliation delays disappear.
Detailed page → BIA management dashboard showing real-time profitability per trip and vehicle, lane metres, cost per km, empty-return rate and the direct-indirect cost breakdown on one screen.
Detailed page → IoTA layer that compares CANbus consumption with pump-receipt data for deviation alarms, driver behaviour scores and cold-chain temperature tracking, connected to accounting.
Detailed page → MobilAn offline-capable mobile app collecting delivery notes, CMR, delivery photos, expense receipts and proof of delivery; it replaces WhatsApp and paper receipts.
Detailed page → PortalA web/mobile portal where customers track their loads with live location, ETA and documents on their own; it reduces the call-centre load.
Detailed page → OtomasyonA module that automatically collects completed trips by route and rate and produces periodic settlements, e-reconciliation and payment lists; the month-end argument ends.
Detailed page →Alerts and missing-declaration blocking for TIR carnet/ECMT stock-usage-returns, U-ETDS and NCTS declarations, vehicle inspection-insurance and driver SRC/licence expiry dates.
A load/order pool, fast quotation-booking, customer-specific tariffs and trip history; customer management that brings sales and operations into one flow.
Detailed page →A module connecting bonded-warehouse entry-exit, RF handheld stock, goods receipt notes and carrier-based commission tracking to the trip and accounting side.
Your finance and accounting backbone (Logo, Mikro, Netsis or SAP) stays in place; your e-Invoice, e-Delivery note and receivables order is never disturbed. The operational layer we build talks through your ERP's API or database, and pulls km and fuel data from your vehicle tracking system's (Arvento, Mobiliz) service. Trips, accounts and fuel are gathered in a single source of truth, and operational data flows into it. So you neither end up running a second accounting system, nor keep managing trips in Excel.
Our integration approach →We discuss your fleet (owned/subcontractor mix), your transport profile (domestic, international TIR, cold chain), your current ERP and the operational point that hurts most. We clarify expectations and scope and draw a realistic frame; at this stage understanding, not selling, comes first.
We observe the operations centre, the trip-planning flow, the fuel and settlement spreadsheets and driver-office communication on site. We surface the data gaps between Logo/Mikro/Netsis/SAP, the TMS and Arvento; we map cost, reconciliation and compliance gaps.
We turn the discovery findings into a prioritised roadmap: which module first, which integration connects where, which gain arrives first. We present a clear plan that protects your ERP, is module-based and phased to your budget.
We start with the module that produces the most value (usually the integration bridge, trip profitability or subcontractor settlements) and develop iteratively. At the end of every sprint we show a working release; we fine-tune with feedback from the operations team and managers.
We put the system live in the operations centre and in the field; we train planners, accounting staff and drivers by role. After go-live we stand by you with maintenance, SLA and development support. Source code and data stay entirely with you.
We know Gaziantep's road logistics context and the trip-fuel-settlement reality; we build solutions by talking through the operations centre and the driver flow. We listen first, then write.
Your Logo, Mikro, Netsis or SAP backbone stays in place. We build the operational layer that works alongside it and closes the accounting-operations-telematics gap; your existing order is not disturbed.
Even two firms — one running domestic groupage, one running international TIR — are not the same. We write to your trip flow, your subcontractor model and your tariff structure; we carry no unnecessary features.
The source code of everything we build and all the data belong to you. You are not locked into one supplier; you can carry on with another team later if you wish.
This sector's real problem is not any single program but the disconnect between systems. We make bridging accounting, the TMS and vehicle tracking the heart of the solution.
We do not force you to build everything at once. We start where it hurts most, show the gain, then grow; we spread your budget across phases and lower the risk.
No. Your accounting and finance backbone stays exactly as it is; your e-Invoice, e-Delivery note and receivables order is not disturbed. The trip, fuel, settlement and traceability layer we build talks to it through your ERP's API or database. The aim is not to install a second accounting system, but to connect the operation the ERP cannot see to it.
Yes. We pull km, location and CANbus fuel data from the services of Arvento, Mobiliz and operator vehicle tracking systems and connect them to the trip and cost side. Telematics data no longer sits in a separate portal; trip profitability, fuel leakage detection and driver behaviour scores appear in the same picture as accounting.
To the km and fuel data coming from telematics we add direct costs such as HGS motorway tolls and driver advances and expenses, and indirect costs such as depreciation, insurance, maintenance and overhead shares. The result is real-time profitability per trip and vehicle, plus the lane-metre figure. You see where the money is being lost before the trip is even closed.
Yes — in fact, that is the profile that benefits most. You do not need to buy a separate TMS; we run trip operations directly in this layer and integrate it with your existing accounting ERP. The trip, fuel and settlement processes running on Excel and WhatsApp move into a single system.
We collect completed trips automatically by route and rate. Which subcontractor ran which trip, how many trips have accumulated and how much the settlement comes to is visible in real time. At period end, the settlement, e-reconciliation and payment list are produced automatically; collating in Excel and the month-end dispute disappear.
Yes. We build a web/mobile portal where customers watch their own loads with live location, estimated arrival (ETA) and documents (CMR, e-Delivery note, POD). 'Where is my load' calls fall, your operations centre's workload lightens, and the visibility you give customers turns into a competitive edge.
Yes. We set up a compliance calendar for TIR carnet and ECMT (UBAK) logbook stock-usage-returns, U-ETDS and NCTS/T1-T2 declarations, vehicle inspection-insurance and driver SRC/licence/psychotechnical expiry dates. It raises automatic alerts and blocks missing declarations; the risk of dispatching with an expired document and of penalties drops.
The source code of everything we build and all the data are one hundred per cent yours. You are not locked into one supplier; you can carry on with another team later if you wish. We want the reason you work with us to be that we know the field, not that you have no choice.
Let us observe your operation on site, from trip planning to the fuel and settlement spreadsheets, from driver communication to customer visibility. Without replacing your existing ERP, let us draw up a realistic roadmap that starts where it hurts most. The first step is a discovery meeting.
