EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

ERP · Kartal

ERP for Kartal businesses

Kartal's manufacturing strip along the coast road sits beside the service floors around the health campus. If your maintenance crew drives straight to the first job in the morning and the office has shut before they get back, the two sides never share a desk inside a working day; split the record between them and the line the office bills stops matching the job the field closed. That split is what ERP software in Kartal, Istanbul has to answer. AlgoKlima answers it with two interfaces over one set of records: whatever row the phone writes to is the row the panel reads.

Get a quote Tell us about your project

ERP — Kartal

Manufacturers around Soganlik and service floors near the health campus stand close together in Kartal. Where the work happens on someone else's premises and the record is kept at the office, the distance between them has to be closed every evening. The work closest to this district's sector profile is AlgoKlima, our own product, whose releases and upkeep stay with us. Where it does not overlap: written for air conditioning, boiler and appliance service, it has nothing to show for a bench schedule or a material requirements plan. The scope narrows: consolidated finance, human resources, the supply chain and production planning fall outside. What carries is not a screen but how two interfaces hang on one record set. The panel runs on Laravel, Inertia and Tailwind, the field app on React Native (Expo), both against one MySQL database with Redis for reads.

  • The field phone and the office panel hang on one record set, so the job a technician closes is the row an invoice is read from.
  • Changes reaching one job from both directions are processed in the order they were made and merge into a single record through conflict resolution, so nobody picks between two copies.
  • The limit is written down: AlgoKlima was built for service work, and a production order, a bench schedule or a material requirements plan sits outside it.

Why Algoriel

  • Work order through to invoice

    In AlgoCar information is entered once and carried on the same record from the work order to the invoice.

  • Stock moves next to the job

    Parts leave stock against a work order, so nobody hunts for where a part went at month end.

  • The calculation becomes the quote

    Resterm sizes a unit with an engineering calculation, and the result drops into the cart and the project record.

  • Where the scope stops

    Operations, stock and accounting are in scope. Production planning, supply chain, consolidated finance and HR are not.

What we build

ERP

  • Work order, part and invoice on one chain

    At AlgoCar a work order opens, the part consumed is written to it, and the invoice comes from that same record. The chain never splits across three programs.

  • The same movement is never typed twice

    A part leaves stock the moment it is written to the work order. No warehouse screen sits waiting for the same consumption to be keyed in again.

  • Cost and revenue in one system

    The trading and accounting side runs in the same system as the service record, so the two faces of a job are not reconciled after the fact.

  • Spend that accumulates on the asset

    At AlgoCar servicing and repair build up under the plate and chassis record, so what a vehicle has cost in total is read from its own file.

  • Where a quote line came from

    At Resterm you can trace a quote line back to the heating requirement that produced it.

  • From calculation to basket to project

    The product the engineering calculation selects drops into the basket, the basket attaches to a project, and the project to its customer. The records stay on one chain.

Work like this

ERP · Case study

AlgoKlima — two interfaces, one record set: field and office write the same row

AlgoKlima is our own product for air conditioning, boiler and appliance service, and we carry its upkeep. The office panel runs on Laravel with Inertia, the field app on React Native (Expo); both sit on one MySQL database with a Redis cache. Two interfaces do not mean two ledgers: the job a technician closes on the phone is the row the office bills from. A record opened out of coverage goes to the phone's local queue first; when the connection returns the queue drains in the order it was created, and changes from both directions merge into one record through conflict resolution. Production orders and bench schedules stay outside it.

Read the case study →

Working with Kartal teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • If the field and the office update one job at the same time, which version survives?

    Neither has to be chosen, because there is one record. Changes from the field queue on the phone in the order they were made, the queue drains that way when the connection returns, and corrections from both directions merge into the same row through conflict resolution.

  • AlgoKlima was written for air conditioning service. What does a manufacturer take from it?

    That it is service software, plainly: a bench schedule or a production order is not work we can show. What overlaps is not the equipment but the way one job record is shared by two interfaces. Rename the container and the field and the office still write to the same row.

  • When you say ERP, does that reach production planning or payroll?

    It does not. The scope is operations, stock and accounting. Production planning, the supply chain, consolidated finance and human resources are areas we have nothing to show for, and we do not promise a module we cannot demonstrate.

  • Our crews are on the road all day around Kartal's manufacturing strip. Would you not have to come out and install it?

    No. We have no office to work from and we do not attend sites. Because AlgoKlima is our own product, the discussion is not about installation but about which record each piece of information will sit on, and we put that down in writing together.

ERP in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Is the cost of a job still meeting its revenue at month end?

Get a quote or open the service