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

Process Tracking for Catalca businesses

In a food business today's list is wrong by tomorrow. A price moves, a delivery differs, the board gets written over. What was written over is gone too, so at the close of a season there is nowhere to look up what changed and when. That is the question sitting under process tracking software in Catalca. Günlük Hava Durumu ties three stages of one record together: the day on air, the day handed to the archive, and the summary computed from it.

Get a quote Tell us about your project

Process Tracking — Catalca

Catalca runs on food retail and rural trade, mostly businesses the owner works in personally, with outlets spread between the town centre and the village roads. Merkez Kasap is here and we wrote its QR menu, a match we cannot claim in any other district. That job was a menu page, though, and proves nothing about tracking a process. The evidence here is Günlük Hava Durumu, and its boundary is plain: written for weather and climate data, with no ordering or stock layer, and we have never built farming or livestock software. What carries is how the stages of a record stay linked. Laravel renders the pages, MySQL holds the day records, React carries the interface.

  • The day on air refreshes and the shown value is overwritten on the next update, then its date passes and the same record hands itself to the archive rather than vanishing.
  • An archive row is written once and never edited, so a forecast gives way to a measured day and looking back shows what stood on which date.
  • The summary comes from no second source: it is computed from the archive rows, so it renews itself as the archive grows instead of waiting on a manual update.

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

Günlük Hava Durumu — a day on air hands itself to the archive a summary reads

A site publishing weather and climate data, where three content types are links in one chain. The forecast page refreshes and the value shown is overwritten on the next update. Once that day's date passes, the record hands itself to the archive: every past day keeps a permanent address of its own, written once and never edited afterwards. The climate summary arrives from no separate data source; it is computed from those archived day records and renews itself as the archive grows. Laravel renders, MySQL stores, React carries the interface.

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

  • Have you actually built anything for a business in this district?

    Yes. We wrote the QR menu for Merkez Kasap, a butcher shop genuinely in Catalca. That job was a menu page, with no ordering, payment or stock. On the process tracking side the evidence is Günlük Hava Durumu.

  • What do we lose by writing over old records instead of keeping them?

    The ability to compare. A value written over is not there when you go back, and nobody can show what stood on a given day. With the chain in place, the day on air refreshes while the day whose date has passed turns into a row that no longer changes.

  • Would it not be simpler to keep the summary report somewhere separate?

    A summary kept apart waits for someone to update it and drifts from its source. On Günlük Hava Durumu the summary is computed from the archive rows, so it renews as the source grows and two figures never part company.

  • We sell food. What does a weather site tell us?

    Not the sector, but how long a record lives: the state on air, the archive row that stops changing, and the summary computed from it. Farming and livestock software is something we have never written, and we say that up front. The team works remotely; nobody travels to the district.

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