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

Management Systems · Catalca

Management Systems for Catalca businesses

Work in Catalca does not always stay at one address. A crew can be in a shop in the centre one day and out towards Yalikoy or Ovayenice the next. Nobody installs a turnstile at a point the team will have left by tomorrow. The construction site attendance system was written against exactly that: entries and exits are recorded with a QR code and a location, and the record holds not only how long somebody stayed but which point they stayed at.

Get a quote Tell us about your project

Management Systems — Catalca

Trade in Catalca runs on food retail and rural commerce, and work can spread between the centre and the village roads, so one crew touches several points in a week. One business here we can name with the district: Merkez Kasap. We wrote its menu page, but that job carries no staff record and is not this page's evidence. The evidence is the site attendance work, and where it stops is plain: written for construction sites, with nothing to show on food production, farming or livestock, and payroll and statutory timesheets outside the scope. What carries across: one person's hours at different points never melt into a single total. The app runs on the phone with React Native (Expo); Laravel takes records, MySQL keeps them.

  • The QR code establishes who scanned and the location establishes where they were, so the site name is never picked from a list and the record cannot drift from the real place.
  • Hours at different points are totalled separately, so a crew member who touches several places in a week does not disappear into one lump sum.
  • Duration comes out of a matched entry and exit pair; an entry whose exit was never scanned stays visible as an incomplete record instead of counting as finished.

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.

What we build

Management Systems

  • 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

Site attendance — the record also holds who stayed at which point

A site is temporary: no turnstile goes up, and workers move between them. Entry and exit are written with a QR code and a location: the code says who scanned, the location which site, and no name is picked by hand. Duration comes from a matched pair; an entry left open stays incomplete until its exit is scanned. Earned time is not held in a spreadsheet; it comes from those pairs, and one person's hours at different sites total apart. The app runs on the phone with React Native (Expo); Laravel receives records, MySQL keeps them; nothing is left to unbolt when a site closes.

Read the case study →

Working with Catalca 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 crew visits several points in one day. How do the hours separate?

    They separate on their own, because every entry is written with its own location. When somebody leaves the point in the centre and starts at one on a village road, a second record opens. What you read at the end of the day is not one figure but hours standing point by point.

  • Why not let people pick the site name from a list? It would be quicker.

    A name picked from a list is a claim; a location is evidence. Manual selection folds mistaken taps and later corrections into the record. Reading the QR code and the location together closes the entry in one step, so no second approval stage has to exist to verify it.

  • Our payroll program works. Do we have to replace it?

    No. What we describe is not payroll itself but where the hours that feed it come from. Earned time is produced from closed record pairs rather than kept in a second spreadsheet. We also say plainly that we have nothing to show on payroll or statutory timesheets.

  • You did the Merkez Kasap job in Catalca. Would ours be the same thing?

    No. That one was a QR menu page — no orders, no payment, no staff records were ever built into it. What this page describes is independent of it: an entry record that is created together with its location, and hours that separate point by point.

Management Systems in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

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

Get a quote or open the service