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

ERP for Sisli businesses

Retail habit treats what is sold as a single line: one item, one price. In Sisli the cosmetic shopfronts around Nisantasi and the central trade offices near Tesvikiye stand side by side, and where what you sell runs over several steps that habit breaks, because a line gives no sign of how many steps sit behind it. What is sold is not a procedure but a structure showing which tooth gets which treatment, and that structure splits into ordered sessions. In the CRM we built for a dental clinic the plan stands as its own record rather than inside the appointment.

Get a quote Tell us about your project

ERP — Sisli

Sisli leans on the shop window: cosmetics retail, central trading and service floors sit together. Where a service cannot be represented by one line, the difficulty starts there. The work closest to how this district runs is a CRM we built for a dental clinic. Where it does not overlap is worth stating: it was written at single-clinic scale, and we have nothing to show for shelf counts, store tills or chain-store management. Production planning, consolidated finance, human resources and the supply chain sit outside the scope. What travels is the shape of the record: the work splits into named steps, and because the treatment applied lives on the patient record, what is invoiced is read from the same place. Laravel runs the process; MySQL holds the plan, treatment and invoice records.

  • The plan is built tooth by tooth: the treatment for each tooth is written as its own step, and the steps are spread across ordered sessions.
  • A treatment sold is not a single line — how many steps it holds and which of them were applied are read from the same patient record, with no second list kept alongside.
  • The boundary is written down: the work stayed at single-clinic scale, and we have no chain-store stock or production schedule to show.

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

Dental clinic CRM — treatment stands as its own record, built tooth by tooth

A system built for a dental health clinic. What sets it apart is where treatment is written: the plan is built tooth by tooth, the work for each tooth stands as its own step, and the steps are spread across ordered sessions. Treatment becomes a record in its own right rather than something inside the appointment, so what is sold shows how many steps it holds. Because the treatment applied lives on the patient record, the invoiced work is read from the same place, and reports read it from another angle. Laravel runs the process; MySQL holds the plan and invoice records. Scale is a single clinic; chains and hospitals stay outside.

Read the case study →

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

  • We are looking for ERP but we do not manufacture. What is this evidence worth?

    It rests on the work and its money coming out of one structure. The plan is built step by step, the step applied sits on the patient record, and what gets invoiced is read from there. Production scheduling, material requirements planning and the supply chain are things we cannot show, so we do not promise them.

  • Could we not write the programme we sell as a single line?

    You can, but then nobody sees how many steps were delivered. With the plan built tooth by tooth, which step is done and which is waiting come off the same record. A single line does not carry that split; a person's memory does.

  • We are in cosmetic retail in Sisli. Does the shelf and till side come with it?

    It does not. There is no store till or shelf count in the portfolio, and this page's evidence stays on the clinic side. We say so up front rather than sign off a module with nothing behind it.

  • Our clinic is in Pangalti. Do you not need to set it up on site?

    No. There is no office for anyone to visit, the team is spread out, and the work runs remotely. What matters is not the number of chairs but how a treatment divides into steps, and that lives in the plan structure.

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