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 · Umraniye

ERP for Umraniye businesses

Umraniye's Dudullu industrial estate holds mechanical contracting, air conditioning service and light manufacturing side by side. Split your work into planned maintenance and breakdown calls and both still draw parts from the same shelf. So the ERP question in Umraniye is not which suite to install; it is which record a part leaves the store on. AlgoCar was written against that question — our own product, whose upkeep we carry, not a client handover.

Get a quote Tell us about your project

ERP — Umraniye

Service work and light manufacturing sit next to each other in Umraniye: a plant commissioned one season can turn into a breakdown call the next, with one store supplying both jobs. The work closest to this district's sector profile is AlgoCar. It was written for vehicle servicing; what travels out of it is the shape of the record, not the screens. Where manufacturing is dense, ERP is usually asked with production planning in mind, and that is not where our scope sits. Production planning, supply chain, consolidated finance and human resources are outside it; operations, stock and accounting are inside. Laravel runs it, Inertia carries the interface, MySQL holds the records and Redis the cache — the same foundation from one project to the next.

  • A breakdown call and a maintenance job are managed as separate work types, and both draw on one parts store, so a second stock system never has to exist.
  • Trading and accounting sit inside AlgoCar's own scope, so closing a job starts no transfer into another program and no reconciliation between two systems.
  • What we do not promise is written down too: supply chain, production planning, consolidated finance and human resources fall outside this scope.

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

AlgoCar — the work order carries the part, service and maintenance share one store

Our own product: a vehicle service system whose upkeep we carry, not a client handover. The chain runs on one record: a work order opens, the part consumed is written to it, stock falls at that moment, and the invoice comes off it. No second line waits on the warehouse side. Breakdown calls and maintenance work run as separate work types, yet both attach to one parts store and one accounting side, so nothing needs reconciling later. The plate and chassis record marks AlgoCar's vehicle context; the record's shape is what travels.

Read the case study →

Working with Umraniye 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

  • You say ERP. Does that cover production planning?

    No. The scope covers operations, stock and the accounting side. Human resources, consolidated finance, the supply chain and production planning sit outside it, and we do not promise what we cannot show.

  • We are a mechanical contractor in Umraniye running air conditioning service, not a vehicle workshop. What does AlgoCar say to us?

    AlgoCar is vehicle service software and we say so plainly. What carries across is not the vehicle screens but how the record is shaped: the work order is a container, the part consumed is written into it, and the invoice comes off the same record. Rename the container a unit or a plant and the chain holds.

  • Would you not need to visit our workshop and watch the process?

    We do not need to. We work without an office and without site visits. Rather than watch a floor, we write down together where each record starts: where a maintenance job separates from a breakdown call, and which entry the parts store answers to.

  • We already run a stock program that works and do not want to drop it.

    The program is not the question; where the movement is recorded is. If a part is typed into the warehouse program and again into the work order, that second entry is the problem. With one entry point the gap stops waiting for month end.

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