Get a quote

ERP · Istanbul

ERP for Istanbul businesses

Keep the work order in one program, the parts store in a second and the invoice in a third, and the same consumption gets typed twice while the gap between the records waits for the month to close. For anyone weighing up an ERP software company in Istanbul, the question worth asking is where those three records meet. We wrote AlgoCar as our own product so that chain would sit on one record. Nothing here is a suite we resell.

ERP — Istanbul

Istanbul carries a heavy concentration of service, maintenance and after-sales work, and one job often moves between several points before it closes. The work closest to this market's sector profile is AlgoCar, our own service management software, built around the vehicle in the workshop rather than the customer who brings it. Laravel holds the process, Inertia the interface, MySQL the records and Redis the cache. We do not pick a stack per project but one we can still maintain years from now. The scope stays where the evidence is: operations, stock and accounting. Production planning, supply chain, consolidated finance and HR sit outside what this portfolio can prove.

  • Writing a part to the work order takes it out of stock at that moment, so no warehouse screen waits for the same line twice.
  • Spend gathers under the plate and chassis record, not a customer card, so a vehicle carries its history when it changes hands.
  • Trading and accounting run inside the same application as the service record, so cost and revenue meet as the job closes.

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 — built around the vehicle: one record from work order to invoice

Work in a vehicle workshop starts when a car comes in, and the record scatters straight after. AlgoCar puts the vehicle at the middle instead of the customer: the plate and chassis record is where the service side and the commercial side meet. A work order opens, the part consumed is written to it and leaves stock at that moment, and the invoice comes from the same record. Servicing and repair spend collects on the vehicle's own file. AlgoCar is not client work — it is an Algoriel product, and we carry its maintenance.

Read the case study →

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

  • How do you work with a business in Istanbul without an office there?

    We keep no office at all and work remotely. In AlgoCar, which record a cost lands on is settled in writing before any code is written, and that decision is made on a shared screen. The city your business sits in does not change how its records are chained.

  • Are you building a full ERP?

    No. What we describe is operations, stock and accounting closing on one record. Production planning, supply chain, consolidated finance and HR are areas we have nothing to show for, and we say that instead of promising them.

  • Why should stock not stay in its own program?

    A separate program means entering the same movement twice. In AlgoCar a part leaves stock as it is written to the work order, so nothing waits on the warehouse side. Keep the two records apart and the difference only turns up at stock count.

  • Our product needs an engineering calculation before it can be quoted. Does that fit?

    It does. At Resterm the product the calculation selects goes straight into the basket, the basket attaches to a project, and the project to its customer. You can read a quote line back to the input behind it.

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