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

Management Systems · Basaksehir

Management Systems for Basaksehir businesses

A mould shop asks for a consumable by its properties, never by its code: someone says a diameter and a hardness, and the person at the bench pulls the right box. Put that same request into a management system and it stalls, because the only way into the item list is a category tree, and the tree assumes you already know the code. Machine build and tooling work run dense around Basaksehir's Ikitelli estate, so the question here is narrow: can a record be reached from a property? Kokudankokuya answers it with a second axis.

Get a quote Tell us about your project

Management Systems — Basaksehir

In Basaksehir, what sits in the cabinet beside a bench is rarely one product; it is one part held in several sizes. The closest match in our portfolio is Kokudankokuya. Where it does not overlap comes first: it was written for perfume retail, so work orders and production schedules were never built there, and warehouse operations and dispatch planning fall outside it as well. What carries across is the shape of the catalogue. A scent stays one product record, volumes are separate sellable units, and price and stock hang off the volume. The shop runs on Laravel and MySQL; its scale never called for a search layer of its own.

  • Two routes reach the same record: the category tree is one, fragrance family and note are the other, and the second route is what works when nobody knows the brand name.
  • A perfume can hang off more than one note, so it never sits trapped on a single branch and the same record surfaces from different search intents.
  • Because the volume is the sellable unit, price and stock are held at that level; the scent record stays single and a new size is not a new product in the catalogue.

Why Algoriel

  • Capacity and credit stay apart

    Pilatesco keeps class capacity and a member's remaining package credit as two different things, so filling one does not quietly consume the other.

  • The same data is entered once

    In AlgoCar service, stock and accounting read the same record, so nothing gets retyped into a second screen.

  • Reports come off the record

    Invoices and reports derive from the work that was logged, so no separate month-end sheet has to be filled in.

  • Sale and use meet on one record

    At Pilatesco an invoice is raised when a package is sold while use is read from a calendar spread over weeks, and both meet on the member's record.

What we build

Management Systems

  • The rule is written into the record

    What each situation leads to is defined in advance. At Pilatesco a cancellation, a no-show and a completed session each hit the entitlement differently, and nobody decides on the spot.

  • Capacity is more than a single number

    How many people an hour holds is worked out from the instructor, the equipment and the time together. A one-to-one session and a group class open under their own rules.

  • Where the work stands, on one screen

    At AlgoCar a job moves along one record from the moment it opens to the moment it closes. In the dental clinic the manager sees which step of the plan a patient has reached without leaving that screen.

  • One record, seen to the limit of each role

    Vipkurum keeps timetables, classes, exams and payment records in one place, and a teacher, a guardian and an administrator each reach that record at their own permission level.

  • A report is the same record from another angle

    The month-end picture does not require a second set of books; it is the sum of what was recorded during the day.

  • A team that does the maintenance daily

    AlgoCar and AlgoKlima are our own products and both are live. We do the maintenance on software of this kind every day in our own panels, so it is not a promise we make for after handover.

Work like this

Management Systems · Case study

Kokudankokuya — one scent record, volume as sellable unit, note as second axis

A perfume shop whose catalogue follows the logic of the shelf: a scent is one product record, volumes are separate sellable units, price and stock hang off the volume, and adding a size opens no new product. Beside the category tree, fragrance family and note open a second axis, so a customer who cannot name the brand starts from a scent's character and reaches the bottle. A perfume attaches to several notes, which is why one record answers to different searches. The catalogue's scale asked for no separate search or cache layer; the shop sits on Laravel and MySQL.

Read the case study →

Working with Basaksehir 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

  • Our products are the same part in different sizes. Does each size need its own card?

    No. In Kokudankokuya the product stays one record and the sellable unit lives one step below it, which is where price and stock are kept. Adding a size means adding a unit under an existing record, not opening another product.

  • We already have a search box. Why does the catalogue need a second axis?

    A search box serves whoever already knows the right word. Someone who cannot recall a code or a brand does not know what to type into it. The second axis is for that person: the record is reached from a property, starting at the character and ending at the item.

  • We run a mould shop in Basaksehir and you are describing a perfume store. What does that tell us?

    Not the screens — the shape of the record. The product is a container, the sellable unit sits inside it, and navigation is not tied to a single tree. Call the container a cutting tip or a profile instead of a bottle and the structure holds. We say just as plainly that we have nothing to show on the manufacturing steps themselves.

  • Who does the work, and where do you sit?

    We hold no physical address and the work runs remotely from start to finish. Kokudankokuya was written by two teams: ours, and one we work with regularly. The first thing we hand over is written, not code: which distinctions the catalogue will be built on.

Management Systems in other cities

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

Other services for this location

Which rule in your business still depends on somebody remembering it?

Get a quote or open the service