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

Process Tracking for Beylikduzu businesses

On a sales floor the conversation keeps turning at one point: a buyer standing beside a machine asks about a new one and a used one in the same breath. Most catalogue setups answer that in two separate lists, and the comparison ends up in the salesperson's head. Anyone shopping for process tracking software in Beylikduzu meets the same question underneath. Is condition a field on the record, or a catalogue of its own? On Plastik ve Makina it is a field.

Get a quote Tell us about your project

Process Tracking — Beylikduzu

Beylikduzu's texture is showroom and sales floor. If a sale runs between a screen and a floor, the buyer opens the list on a phone while standing beside the machine body. The closest work to that sector profile is Plastik ve Makina, written for trade in plastics processing machinery. It is a listings platform, not a shop: no basket, payment or stock was ever built into it. Work orders, field crews and attendance records fall outside it too, so that face of process tracking is not shown here. What it shows is the catalogue: the tree is cut to one machine family's own divisions, and condition rides on the listing. Laravel prepares the list on the server, MySQL holds listings, Redis the cache, Inertia and Tailwind the interface. We work remotely and install nothing on a showroom floor.

  • The category tree is cut to the divisions of one machine family, so a distinction that would be a subheading on a general listings site becomes the main axis here.
  • New and used machines are never split into two catalogues: condition is a field on the listing, so a buyer weighs both inside a single search.
  • Changing a filter refreshes the results in place — Laravel prepares the list on the server and Inertia carries it over without reloading the page.

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

Plastik ve Makina — condition as a field, a tree cut to one machine family

A sector listings platform for those who buy and sell plastics processing machinery. The category tree is cut to one machine family's own divisions: what would be a subheading on a general listings site becomes the main axis here. New and used are not divided into two catalogues: condition is a field on the listing record, so a buyer weighs both inside a single search. Laravel prepares the list on the server and Inertia carries it over, so a changed filter refreshes results in place instead of reloading. MySQL holds the listings, Redis the cache, Tailwind the interfaces. Basket, payment and stock lie outside this work.

Read the case study →

Working with Beylikduzu 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 keep new and used stock on separate sites. What does one list buy us?

    Buyers already ask about both together. With condition as a field on the listing, the comparison stays inside the search, and the same machine never has to be described twice across two catalogues.

  • Could we adapt a category tree from a general listings site?

    On a general tree your main distinction lands as a subheading, and a buyer searching in their own words never reaches it. On Plastik ve Makina the tree was cut to one machine family's own divisions, so what had been a footnote became the first step of a search.

  • Every filter change reloads the page and we lose the buyer. What answers that?

    The list is prepared on the server and Inertia carries it to the browser. A changed filter refreshes results in place rather than reloading the page. We quote no speed figure, because we have measured none.

  • You say process tracking. Does that include work orders and field crews?

    Not on this page. Plastik ve Makina is a listings platform: work orders, attendance records and field crews were never built into it. The process described here is the listing's own state — which division it sits under and which condition it shows in.

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