Software company in Kocaeli that knows logistics from the inside
Arasix was born inside a logistics company. We built TMS, vehicle tracking, ETA customer portals, operations dashboards and field mobile apps while working with real trips, real vehicles and real drivers. Today we bring the same experience to businesses directly, and to software companies and agencies as a white-label development partner.
Software for logistics and field operations
TMS – Transport management system
Orders, trip planning, vehicle and driver assignment, loading and delivery records, freight and payout calculations in one flow. Operations teams stop re-entering the same data into spreadsheets and ERP.
Vehicle tracking and route management
Follow your fleet on a live map; see route deviations, stop durations and trip history. Location data is matched to trip records in your ERP.
ETA and customer portal
Your customers see where their shipment is and when it will arrive without calling you. Delivery status, documents and notifications live in one portal.
Operations dashboards
Trip, utilisation, delay, fuel and cost indicators in front of management. Decisions from the same data source, without waiting for reports.
Driver and field mobile apps
iOS and Android from a single React Native and Expo codebase. Task lists, photo evidence, signatures and offline work where the connection drops.
ERP and e-invoice integration
Portals and approval flows that work alongside SAP, Logo, Netsis or Mikro instead of replacing them. Scope is set once version, licence and API options are verified.
Up front or behind the scenes: pick the model that fits
Direct projects for businesses
End-to-end development from analysis to go-live for companies with logistics, industrial or field operations.
- Workflow-led discovery
- Phased delivery with regular demos
- Go-live, training and maintenance
White-label development for software companies and agencies
Your client stays your client. We build behind the scenes under your brand, following your processes.
- Work under a non-disclosure agreement
- Your repositories, task and communication tools
- Source code and documentation handover
Modules and maintenance for existing systems
Add a new module, integration or mobile app to software you already run, or hand its maintenance over to us.
- Review of the existing codebase
- Backward-compatible development
- Release and issue tracking
Workflow before the quote
Discovery
Where is data created, who approves it, which system receives it? We map the process with the people who do the work.
Scope and architecture
Screens, roles, integrations and acceptance criteria are written down; time and cost follow from that scope.
Phased development
We show working parts early, so feedback reaches the product before the work is finished.
Go-live and support
Data migration, user training and go-live, followed by ongoing maintenance and development.
Why sector experience matters when choosing a software company in Kocaeli
Gebze, Dilovası, Çayırova and İzmit are where ports, warehouses, transport and manufacturing meet. Software here succeeds when it shortens the work of the person in the field, not when it adds screens. A team that knows why a trip is late, what a driver needs and what the customer keeps asking sets the scope right in the first meeting.
For logistics companies: off-the-shelf TMS or custom software?
An off-the-shelf TMS is a fast start for standard processes. When you need a cooperative queue system, custom freight and payout rules, a customer-specific ETA portal or tight integration with your ERP, custom development or a module next to your existing system usually works better. We make that call with you in the first meeting.
Why is our reference list short?
Much of our work was built for our own logistics operation and as a subcontractor under non-disclosure agreements. So instead of client logos, we show the work itself: our project pages describe the problem each system solves, its modules and the technologies used.
Frequently asked questions
Are TMS, vehicle tracking and an ETA customer portal the same thing?
No. A TMS manages orders, trip planning, vehicle and driver assignments, and operational records. Vehicle tracking supplies location, route and stop information. An ETA customer portal lets customers follow shipment status and estimated arrival; these serve different needs within the same operation.
What information is needed before integrating a TMS with an ERP?
First identify which system owns order, trip, vehicle and financial data, and the direction of each transfer. Review the ERP version, licences, API access, permissions and sample records. Define error and duplicate-record scenarios and acceptance criteria during scoping; identical integration options cannot be assumed for every ERP installation.
How does an e-invoice approval workflow connect to an ERP?
Define the invoice source, reviewing roles, approval steps and status information to transfer to the ERP. Arasix’s e-invoice and multi-tier approval project is an implementation example for this need. ERP version, access options, error scenarios and acceptance criteria must be reviewed before promising the same connection for every installation.
How does an ETA customer portal differ from an operations dashboard?
An ETA customer portal presents shipment location, delivery status and estimated arrival for customers. An operations dashboard helps teams review trips, capacity utilisation, delays, fuel and cost indicators. User access, data sources and freshness information are defined within the project scope.
How does a driver app work without an internet connection?
When offline operation is required, the design specifies which data stays on the device, how it is transferred when connectivity returns and how conflicts are handled. Tasks, photos and signatures are assessed according to the workflow. Offline support is not assumed for every module; the supported actions are agreed during scoping.
Do you work as a subcontractor for other software companies?
Yes. We develop modules, sprints or whole projects for software companies and agencies under their brand. Every engagement starts with a non-disclosure agreement.
In white-label work, do you contact the end client directly?
Not unless you want us to. We agree on communication channels and who joins which meeting with you at the start of the project.
Who owns the source code?
Ownership and handover terms are set out in writing in the contract. Code can be developed in your repositories and processes and is delivered with documentation.
Do you only work with companies in Kocaeli?
No. We bring our logistics and industrial experience from Kocaeli to projects across Türkiye and abroad; meetings can be remote or in person.
Do I need to replace my ERP system?
Usually not. We first review the ERP version, licences, APIs and data access options. A portal, approval workflow or mobile module may complement the existing system; compatibility is not promised before data transfer and acceptance criteria are checked.
Do your mobile apps run on iOS and Android?
Yes. We build for both platforms from a single React Native and Expo codebase; offline use in the field is considered during design.
How are price and timeline determined?
Workflows, users, integrations, data migration and acceptance criteria define the scope. The quote is prepared once these are clear.
Let’s talk about your project, or your client’s
Share your sector, the process you want to fix and the systems you use; together we will work out whether you need a direct project, white-label development or an extra module.