Get a quote

Enterprise & Commercial Software · Kadikoy

Enterprise & Commercial Software for Kadikoy businesses

Will a no-show get the session back? The clinic and studio floors around Kozyatagi and Goztepe in Kadikoy work by appointment. If whoever happens to be standing at the desk answers it, then at institutional scale the risk is not one session but two desks answering differently. Pilatesco settles it inside the record: a booking takes one session off the package balance, and cancelling ahead is not the same movement as never arriving.

Enterprise & Commercial Software — Kadikoy

Small retail and appointment-led service floors are dense in Kadikoy. When a business opens a second room the instructor list grows, and the same package has to hold good in both places. That is where the institutional question starts: where is the rule written down? The work closest to this district's service profile is Pilatesco. Where it does not overlap deserves saying: Pilatesco was written for a sports business, so a separate brand surface per branch, a consolidated financial report across institutions and retail stock counting all fall outside it. What travels is which record a right sits on. It runs on Laravel and MySQL, and we do not re-pick the stack per project.

  • A bought package travels on the customer's own record, and writing a booking into the calendar takes one right off it, so nothing is kept in a ledger beside it.
  • Cancelling with notice and never arriving write different results to that balance, and because a rule decides which of them returns the right, two different desks give one answer.
  • The limit is stated as plainly: this scope covers one business's booking and membership records, while a multi-brand roof, consolidated finance and warehouse counts stay outside.

Why Algoriel

  • Many institutions, one system

    Vipkurum runs seven institutions on the same system while each one keeps its records to itself.

  • Adding one adds a boundary

    Each Vipkurum institution signs in at its own domain under its own brand, so adding one does not mean a second installation.

  • Each branch runs its own work

    A branch marks its own exam sheets, so one broken device does not stall every institution at once.

  • Each role, its own view

    Timetable, exams, students, parents, payments and reporting sit on one platform, and who can see what is settled up front.

  • Each institution signs in through its own domain

    At Vipkurum, seven education institutions open under their own address and their own brand, and the name of the software never appears on a user's screen.

  • No reinstallation for a new institution

    Adding one more institution means writing a definition. No second copy of the system is stood up, and the maintenance stays in one place.

  • Office and field on the same record

    AlgoKlima's office panel and field app read and write the same record. A technician closes the job where there is no signal, and the entry reaches the office panel once the connection returns.

  • Operational and commercial records close together

    At AlgoCar the service record and the commercial record sit in the same system, so the cost of a job and its revenue are not reconciled across two programs.

  • One institution's data stays closed to the next

    Student, parent and payment records stay inside the boundary of the institution they belong to. That boundary is how the system is set up, not a view switched off on a screen.

  • One technical footing we can maintain for years

    Nothing goes into your system that the team maintaining it does not already know. AlgoKlima and AlgoCar are our own products, built on that same footing, and we work on it every day.

Work like this

Enterprise & Commercial Software · Case study

Pilatesco — a booking takes a right off the balance, notice and no-show differ

A booking and membership system for pilates studios: a customer buys a package and the rights left travel on that customer's own record, and the moment a booking is written into the calendar, one right comes off the package. Finishing a session, cancelling with notice and simply not turning up each write a different line to the balance. Which of them hands the right back is set in a rule beforehand, so the decision is not taken at the start of a session, or differently at a second desk. It runs on Laravel and MySQL. Scope: one business's booking and membership records.

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

  • The rule changes whenever the person on the desk changes. How do you stop that?

    By moving the rule into the record. Which situation hands a right back is defined in software, so the person at the desk applies what the record says instead of deciding again. What has to change is a line in a rule, not a habit of conversation.

  • We run a few floors in Kadikoy and each keeps its own ledger. What does joining them mean?

    It means attaching the package balance to the customer record. Wherever a right is used, it comes off that one record, so no second ledger survives. The number of floors does not change how we work: we keep no office and run the job remotely from start to finish.

  • We are not a studio but a service point that works by appointment. What does Pilatesco say to us?

    Pilatesco was written for a sports business and we say so plainly. What carries across is not the session screen but how a right attaches to a record: the package sold is a balance, and a booking is a movement off it. Call the container a check-up instead of a session and the chain holds.

  • You say enterprise software. Does the same hold for a group with several brands?

    It does not. Pilatesco carries one business's records. A roof wanting its own domain and brand surface per institution is a different scoping job, and we describe that one through Vipkurum. What we describe here is narrow and concrete: package, booking, balance.

How many institutions and branches should we plan your system around?