Get a quote

Management Systems · Tuzla

Management Systems for Tuzla businesses

A used press arrives in the yard and the record usually says one word: machine. Where it came from is common knowledge for a week and forgotten by the sixth month. Heavy industry runs dense in Tuzla, and where that detail is missing it shapes the maintenance decision and the resale decision alike. Plastik ve Makina is why we can talk about it at all: condition never becomes a second list there, it stays a field sitting on the record.

Management Systems — Tuzla

On the heavy manufacturing side of Tuzla, around the Aydinli line, a machine park grows mixed. One bench is bought new, the next arrives used, and both land in the same list. Split that list in two and the comparison people need disappears with it. The work closest to this district's texture is Plastik ve Makina, a trade listings platform for plastics processing machinery. Where it does not reach is worth stating: we have no marine or shipyard software to show, and shift rosters and production planning sit outside this work too. What carries over is narrow. Condition is a field on the record, not a heading that cuts the list in half. Laravel assembles the list on the server, MySQL stores the listings, Redis takes the cache, Inertia and Tailwind carry the interfaces.

  • New and used sit in one list. Because condition is a field on the record, a buyer weighs both inside a single search rather than opening a second catalogue.
  • Narrowing the list does not reload the page: it is assembled on the server and only the results refresh, so a shop-floor tablet is never left waiting on a fresh load.
  • The boundary is written down: basket, payment collection and stock counting are not part of this evidence, and the deal is settled between the two parties.

Why Algoriel

  • Capacity and credit stay apart

    Pilatesco keeps class capacity and a member's remaining package credit as two different things, so filling one does not quietly consume the other.

  • The same data is entered once

    In AlgoCar service, stock and accounting read the same record, so nothing gets retyped into a second screen.

  • Reports come off the record

    Invoices and reports derive from the work that was logged, so no separate month-end sheet has to be filled in.

  • Sale and use meet on one record

    At Pilatesco an invoice is raised when a package is sold while use is read from a calendar spread over weeks, and both meet on the member's record.

  • The rule is written into the record

    What each situation leads to is defined in advance. At Pilatesco a cancellation, a no-show and a completed session each hit the entitlement differently, and nobody decides on the spot.

  • Capacity is more than a single number

    How many people an hour holds is worked out from the instructor, the equipment and the time together. A one-to-one session and a group class open under their own rules.

  • Where the work stands, on one screen

    At AlgoCar a job moves along one record from the moment it opens to the moment it closes. In the dental clinic the manager sees which step of the plan a patient has reached without leaving that screen.

  • One record, seen to the limit of each role

    Vipkurum keeps timetables, classes, exams and payment records in one place, and a teacher, a guardian and an administrator each reach that record at their own permission level.

  • A report is the same record from another angle

    The month-end picture does not require a second set of books; it is the sum of what was recorded during the day.

  • A team that does the maintenance daily

    AlgoCar and AlgoKlima are our own products and both are live. We do the maintenance on software of this kind every day in our own panels, so it is not a promise we make for after handover.

Work like this

Management Systems · Case study

Plastik ve Makina — condition is a field on the record, so the list never splits

A trade listings platform for people buying and selling plastics processing machinery. The decision that matters happens when the new and used versions of one model can be priced against each other, which is impossible once they sit in separate catalogues. So condition never became a catalogue. It stayed a field on the listing record, and search uses it to narrow rather than divide. The category tree is cut from one machine family's own distinctions, not a broad industrial heading. Laravel assembles the list on the server and Inertia carries it, so narrowing refreshes results in place. MySQL stores, Redis caches, Tailwind shapes.

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

  • Our machine list keeps new and used in separate files. Would merging them cause confusion?

    Separate files are not what keeps them apart; the field on the record is. With condition held as one field the list stays whole and divides the moment somebody asks it to. Separate files add a second matching step, and not only in search — the same step reappears in every report.

  • We work in a shipyard in Tuzla. Do you have anything for the marine side?

    No, and we say so plainly. We have no marine or shipbuilding software to show. What we can describe is the shape of a machine record: how condition, category and search hang together. Whether that maps onto your side is something we look at together, and if it does not, we write that down too.

  • The tablet on the shop floor is slow. Does the page reload every time a filter moves?

    No. The list is assembled on the server and carried to the browser, and a changed filter refreshes only the results block. Someone touching that screen with an oiled glove is not left waiting for a whole page to come back.

  • Would you not need to walk the yard and see the machine park?

    There is no office of ours and no on-site call-out. Instead of walking the park we write down together which piece of information lives in which field: whether condition, model, seller and published state are separate fields or squeezed under a single heading.

Which rule in your business still depends on somebody remembering it?