We take payment up front but the work runs for weeks. How is that read from one place?

The invoice is issued at the sale and usage is read off the calendar, with both attached to one customer record. What was sold and what was done therefore come off a single record instead of two ledgers, and month end brings no reconciliation step.

We run a hotel and a wholesale counter. What does software for a pilates studio tell us?

Pilatesco was written for a studio and we say so plainly. We have no room inventory or order batch work to show. What travels is not the screens but the shape of the record: the sale is written onto a record, and usage is read from the calendar side of that same record.

Payment came in but the work has not happened yet. Where does that gap show?

On the same customer record. What was sold and what has been done so far both sit there, so the gap is not calculated in a separate table. A cancellation, a no-show and a completed session each land differently, and the rule says which is which in advance.

Who does the work, and do you keep a team in Fatih?

We keep no office and the work runs entirely remotely. On Pilatesco the hard part was not drawing screens but deciding which event gives rise to which record, and that decision is made in writing rather than across a table. We start from the same definition with you.

Process Tracking · Fatih

Process Tracking for Fatih businesses

Money arrives on one day and the work happens on others. If you run a guesthouse in Fatih or a wholesale counter along Tahtakale, those two dates do not line up: payment is taken up front while delivery spreads over weeks. Whoever reads the invoice book cannot see how much of the work is done, and whoever reads the calendar cannot see whether the money came in. Pilatesco puts both on one customer record: the invoice is issued at the sale, and usage is read off the calendar.

Get a quote Tell us about your project

Process Tracking — Fatih

Fatih's texture is historic peninsula retail: wholesale food, hardware and guesthouses. The rhythm is not one thing: a guesthouse stacks nights while a wholesale counter pulls orders in batches. Wherever the sale closes in a moment, delivery stretches out. The work closest to this district's sector profile is Pilatesco, written for a pilates studio. Where it does not overlap: room inventory, channel management and wholesale order batches sit outside this product, and we have nothing to show there. What carries is the shape of the record — the moment a sale happens and the place usage is read stay apart, and both meet on one customer record. Laravel runs the process; MySQL holds the customer, sale and calendar records.

The invoice is issued the moment a package is sold, so the date money arrives and the date work happens sit apart and nobody reconciles them by hand at month end.
What was delivered is read off the calendar: each session carries on its own row whether it happened, so sold and delivered are compared from one customer record.
The month-end picture comes off that same record rather than a ledger kept beside it, with what was sold and what has been done so far sitting next to each other.

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

Pilatesco — the invoice is issued at the sale, usage is read off the calendar

Pilatesco handles bookings and memberships for pilates studios. Two timings meet on one customer record: the invoice is issued the moment a package is sold, while usage is read off a calendar spread over weeks. Sold and delivered are never reconciled between two ledgers at month end; both come off the same record. A cancellation, a no-show and a completed session each land differently, and which one restores a credit is written into the rule beforehand. Laravel runs the process and MySQL holds the customer, sale and calendar records. Scope: no room inventory, no order batches.

Read the case study →

Working with Fatih 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 take payment up front but the work runs for weeks. How is that read from one place?

The invoice is issued at the sale and usage is read off the calendar, with both attached to one customer record. What was sold and what was done therefore come off a single record instead of two ledgers, and month end brings no reconciliation step.
We run a hotel and a wholesale counter. What does software for a pilates studio tell us?

Pilatesco was written for a studio and we say so plainly. We have no room inventory or order batch work to show. What travels is not the screens but the shape of the record: the sale is written onto a record, and usage is read from the calendar side of that same record.
Payment came in but the work has not happened yet. Where does that gap show?

On the same customer record. What was sold and what has been done so far both sit there, so the gap is not calculated in a separate table. A cancellation, a no-show and a completed session each land differently, and the rule says which is which in advance.
Who does the work, and do you keep a team in Fatih?

We keep no office and the work runs entirely remotely. On Pilatesco the hard part was not drawing screens but deciding which event gives rise to which record, and that decision is made in writing rather than across a table. We start from the same definition with you.

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

Process Tracking for Fatih businesses

Process Tracking — Fatih

Why Algoriel

Keeps working offline

Entry from QR and location

Records land the same hour

Office and field read one source

What we build

What the record attaches to

The entry that stays open

Who was where, on the record

What is left when the figure is disputed

Records taken beyond coverage

Process rules kept out of the code

Work like this

Pilatesco — the invoice is issued at the sale, usage is read off the calendar

Working with Fatih teams, remotely

Frequently asked

We take payment up front but the work runs for weeks. How is that read from one place?

We run a hotel and a wholesale counter. What does software for a pilates studio tell us?

Payment came in but the work has not happened yet. Where does that gap show?

Who does the work, and do you keep a team in Fatih?

Process Tracking in other cities

Ankara

Istanbul

Izmir

What stands behind your month-end figure today?

Process Tracking for Fatih businesses

Process Tracking — Fatih

Why Algoriel

Keeps working offline

Entry from QR and location

Records land the same hour

Office and field read one source

What we build

What the record attaches to

The entry that stays open

Who was where, on the record

What is left when the figure is disputed

Records taken beyond coverage

Process rules kept out of the code

Work like this

Pilatesco — the invoice is issued at the sale, usage is read off the calendar

Working with Fatih teams, remotely

Frequently asked

We take payment up front but the work runs for weeks. How is that read from one place?

We run a hotel and a wholesale counter. What does software for a pilates studio tell us?

Payment came in but the work has not happened yet. Where does that gap show?

Who does the work, and do you keep a team in Fatih?

Process Tracking in other cities

Ankara →

Istanbul →

Izmir →

What stands behind your month-end figure today?

Ankara

Istanbul

Izmir