Get a quote

Management Systems · Kadikoy

Management Systems for Kadikoy businesses

Small retailers and studios along Kadikoy's Bostanci and Suadiye line can go deep in one family rather than wide across many: the shelf is narrow, the range is not. Off-the-shelf management software arrives with a broad sector heading and a single product dropdown, so the distinctions that actually decide a sale drop into free text and stop being filterable. Plastik ve Makina answers that inside the catalogue, where every branch of the tree grows out of a division the machine family already has.

Management Systems — Kadikoy

Appointment-led businesses and specialist retail sit side by side in Kadikoy, and both can share a shape: few lines, fine distinctions. Where a list is added to through the season rather than set once, a new distinction has to be possible mid-season. The closest match in our portfolio is Plastik ve Makina. Where it does not reach is worth writing down: it is a listing platform for industrial machinery, so appointment books, membership balances and collections sit outside it and we have nothing to show there. What travels is the axis of the catalogue — the first branch comes from the trade's own splits, not from a generic sector heading. Laravel runs it, Inertia carries the list to the browser, MySQL holds the records, Redis takes the read load and Tailwind sets the interface.

  • The first branch opens from a split the trade already makes, so a distinction that would sit as a sub-heading on a general list becomes the first step of navigation here.
  • The list is prepared on the server and handed to the browser, so changing a distinction refreshes results in place instead of rebuilding the page.
  • The limit is written down: appointment books, membership balances and collections are not what Plastik ve Makina demonstrates.

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 — every branch opens from a split the machine family already makes

A trade listing platform built for buyers and sellers of plastics processing machinery. What distinguishes it is where the catalogue comes from: every branch grows out of a division the machine family already makes, so a split that would be a sub-heading elsewhere becomes the first one here. A buyer finds a machine in the terms the trade uses; a seller publishes into that family's catalogue, not a wide industrial heading. Laravel prepares the list on the server, Inertia carries it across, and a change refreshes results without reloading. MySQL holds the listings, Redis the cache. Scope: a catalogue, not an after-sales process.

Read the case study →

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

  • Would an off-the-shelf management tool cover us?

    If the list is shallow and a handful of headings describe it, use one — we say so plainly. The threshold arrives with depth: once a property has to appear in a filter and in a report, free text stops doing the job.

  • Our distinctions shift over time. Can we add to them later?

    The tree is not frozen. Adding a distinction is not the same as opening a second catalogue. On Plastik ve Makina the tree grew with the trade's own splits rather than copying a sector template from outside.

  • Every filter change reloads the page and customers give up.

    The server prepares the list and Inertia carries it to the browser, so a change refreshes results in place. The address moves with the selection as well, which means a filtered list can be shared as a link.

  • We run by appointment in Kadikoy. Are you nearby, could we meet?

    We run without an office, so nobody is dispatched to a site. The first session writes no code; it maps the axes of the catalogue. Which split becomes a branch, which stays a filter, and which is simply a field held on the record.

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