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

Process Tracking · Kadikoy

Process Tracking for Kadikoy businesses

When a machine changes hands its history usually stays in the seller's folder, and the new owner cannot say which part was replaced or when. In a consulting room or studio around Caferaga and Bahariye in Kadikoy the same thing happens on a smaller scale: equipment moves from room to room, sometimes from one business to another, and the service record is left behind. AlgoCar hangs that record on the asset instead. Maintenance and repair sit under the plate and chassis record, not under a customer card.

Get a quote Tell us about your project

Process Tracking — Kadikoy

Kadikoy's texture is service businesses that run by appointment, alongside small retail. If your capital is a single machine, the shape is clear enough: a chair in a consulting room, equipment in a studio, a counter machine in a small shop. Write the service record onto a customer file or into the repairer's own notebook and it detaches the moment that machine moves. The work closest to this district's sector profile is AlgoCar — our own product, whose code and upkeep both stay with us. Where it does not overlap: a studio's class schedule and a clinic's treatment plan fall outside AlgoCar. What carries is what the record hangs on. Laravel runs the process, Inertia serves the screens, MySQL holds the records, Redis carries the frequent reads, and React Native (Expo) runs the phone side.

  • Maintenance and repair are filed under the vehicle's own record, tied to the plate and chassis rather than to a customer card.
  • When the vehicle is sold its file travels with it: nothing is rewritten onto the new owner's card and no second record opens for the same asset.
  • Open a new job and that asset's earlier closings are already in the same place, so a repeat repair shows without anyone checking a separate list.

Why Algoriel

  • Keeps working offline

    The field app keeps recording with no connection, and the queue reaches the server in order once signal returns. That is how AlgoKlima runs.

  • Entry from QR and location

    Where no fixed terminal can be installed, entry and exit are logged from a QR code and a location reading, and entitlement is worked out from those readings.

  • Records land the same hour

    Jobs close in the field, so the office sees where each one stands without waiting for end of day.

  • Office and field read one source

    The office panel and the field app read the same information, so nobody keeps a spreadsheet alongside it.

What we build

Process Tracking

  • What the record attaches to

    Rather than mapping a process in the abstract, we decide what a record hangs on. On the construction system a row belongs to a person and a site at once, and the two are never separated. In AlgoRandevu we are building a structure where a booking can attach to a person, a room or a piece of equipment.

  • The entry that stays open

    Instead of a live dashboard, one rule: a matched check-in and check-out produce the hours, and a check-in with no scan out stays open. Whatever is stuck shows up as that gap.

  • Who was where, on the record

    Because a single row carries both the person and the site, totals separate by site. When one worker spends the month across two sites, those hours never fall into the same bucket.

  • What is left when the figure is disputed

    Because payroll is derived from matched pairs, the number argued over at month end has a time- and location-stamped record behind it. There is no parallel calculation sheet to reconcile against; the dispute happens over the record itself.

  • Records taken beyond coverage

    In AlgoKlima's service flow the chain does not break where the network does. Once the connection returns the waiting entries are processed in the order they were created, and an edit made in the field and one made in the office merge into a single record through conflict resolution.

  • Process rules kept out of the code

    Rules like the length of a step and the gap between consecutive ones belong in a product setting, not in the code. The aim is that changing one does not mean shipping a release, and that is what we are building into AlgoRandevu right now.

Work like this

Process Tracking · Case study

AlgoCar — service history sits on the plate and chassis record, not a customer card

Our own product, built around the vehicle that arrives at a workshop; not a client handover, and its upkeep stays with us. Maintenance and repair are filed under the vehicle's record, tied to plate and chassis rather than to whoever paid. Sell the vehicle and its file goes with it: nothing is rewritten onto the new owner's card. Open the next job and that vehicle's earlier closings are already in view, so a repeat repair does not hide in a separate list. The panel runs on Laravel and Inertia, MySQL holds the records, Redis the reads, React Native (Expo) the field. Scope: vehicle service software.

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

  • We have no vehicles; our capital is equipment. What does this record shape say to us?

    AlgoCar was written for vehicle servicing and we say so plainly. What travels is not the plate screen but what the history hangs on: the record attaches to the asset that was worked on rather than to the person who paid. Call the asset a chair or a bench and the attachment holds.

  • We keep the history on the customer card. What is missing there?

    Nothing, as long as the customer never changes. Move the machine to another room, another branch or another owner and the history stays under the old card, then gets copied across by hand. A copied history is only as complete as whoever copied it remembers.

  • Can our bookings and treatment plans live in the same system?

    AlgoCar does not carry those; they fall outside its scope. We have separate work on the booking and plan side, but that is not what this page describes. What it describes is service history attached to an asset, and we write down what we do not promise.

  • How does a remote team set up a record structure like this?

    We keep no office and the work runs entirely remotely. Setup is not a site visit: first we settle which asset gets a record and which event adds to it, and only then is the rest defined from the panel.

Process Tracking in other cities

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

Other services for this location

What stands behind your month-end figure today?

Get a quote or open the service