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

ERP for Tuzla businesses

Tuzla's shipyard belt and heavy industry run on night shifts, and the certification and refresher training their staff need follows the same beat. Where a course provider splits the day into a night group and a day group, the same person appears in the timetable, the exam list, the payment ledger and the term report separately, and changing a group means retyping every list. Vipkurum stops that scattering at the start: students, parents, the timetable, exams, payments and reporting all sit on one platform. An institution runs one set of records rather than a shelf of separate programs.

Get a quote Tell us about your project

ERP — Tuzla

Work around Tuzla's Aydinli line and the steel halls beyond it turns on shifts. A provider carrying several groups through one term ends up with a timetable, an exam and a payment record for each of them. The institution profile closest to this district is Vipkurum, where seven education institutions share one system, each under its own domain and brand. Where it does not overlap needs saying: Vipkurum was written for how an education institution operates, and we have nothing to show for shipyard production schedules, material requirements planning or vessel maintenance records. The supply chain, production planning, human resources and consolidated finance stay outside. Laravel runs the platform, React the panels and React Native (Expo) the mobile side; MySQL and MongoDB keep the records, Redis the cache.

  • Students, parents, the timetable, exams and payment records sit on one platform, so changing a group never means writing the same person into separate lists again.
  • Each institution signs in from its own domain and its records stay inside that boundary, so a night group and a day group can share a roof without anything opening to the neighbour.
  • The boundary is stated: this evidence sits in how a training institution operates, and we have no production schedule or material plan from heavy industry 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

Vipkurum — an institution's operation does not scatter across separate programs

A platform built for education institutions: several of them share one system and each one's records stay apart. What this page rests on is the gathering — students, parents, the timetable, classes, sections, exams, payments and reporting sit on one platform instead of a program apiece. Invoices, payments and analysis reports come off the administrator's own institution data, and because that boundary is drawn at domain level one institution's records never surface next door. Laravel runs the platform; MySQL and MongoDB keep records, Redis the cache, panels are React and the mobile side React Native (Expo).

Read the case study →

Working with Tuzla 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 run a night group and a day group at once. Does the platform carry that?

    It does. The timetable, classes and sections are defined in the same set of records, so opening several groups in one term is another row of the same structure rather than a new installation. When someone moves group, payments and reporting are not carried over by hand.

  • You say ERP. Does production planning for a Tuzla shipyard come with it?

    It does not. We have written nothing for vessel or shipyard production, and we do not promise past our evidence. What we describe is the institution's own operation: timetable, records, payments and reports closing on one platform.

  • We have several branches. Do they all collect in one place?

    In Vipkurum each institution signs in from its own domain and its record set stays inside that boundary, which is what running several brands on one shared system means. Merging the financial statements of separate legal entities into one report is not in scope.

  • Our team works shifts and cannot sit in meetings. How do you make progress?

    We keep no office and the team works remotely and in writing. What we need is not a site tour but a written decision on which record stays inside which boundary. Progress rests on short agreed notes rather than long calls.

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