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

CMS · Esenyurt

CMS for Esenyurt businesses

Whoever keeps the catalogue current may have no desk of their own, typing between two customers behind the counter. So the measure of a content model is not how many fields a panel offers; it is how many records have to be opened when one size runs out. Esenyurt is thick with small businesses where that cost lands on the owner's own day. If the small size selling out makes the whole item read as gone, the trouble is not stock — it is the level the record is kept at. On Kokudankokuya, price and stock sit on the volume rather than the product.

Get a quote Tell us about your project

CMS — Esenyurt

Businesses in Esenyurt are small and many trade from more than one address, with the person entering data often the same person making the sale. With no IT desk to queue at, how far a single correction spreads is charged straight to the owner's day. The work closest to this district's business profile is Kokudankokuya. Where it stops belongs up front: the shop was built for perfume retail, and transfers between branches, till flow and course enrolment were never part of it, nor was warehouse operation. What we describe is one choice — the sellable unit sits underneath the product. The shop runs on Laravel and MySQL.

  • A scent is held as one record and the volumes sit beneath it as sellable units, so opening a new size never creates a second product entry in the catalogue.
  • Because stock and price are kept at volume level, the large size stays on sale when the small one runs out, and the item never closes as a whole.
  • Beside the category tree, scent family and note open a second way through the catalogue, and one item can hang off several notes instead of being locked to one branch.

Why Algoriel

  • Print becomes editable

    Çatalca Merkez Kasap moved a printed menu to a QR page, so a price change is an edit rather than a reprint.

  • Content gets an address

    Each menu section carries its own address, so a customer can link straight to the section they came for.

  • The institution authors

    Teachers on Vipkurum write their own lessons, tests and exams, so publishing does not wait on a developer.

  • Fixed code, editable page

    QRVizit fixes the printed address once; the page behind it stays editable. We are still building it.

What we build

CMS

  • Content modelling

    Which content types exist, and which fields each one carries, follows your own publishing work. At Vipkurum the assessment type is not hard-coded, so European and Turkish standards sit side by side on the same foundation.

  • The editorial interface

    The person writing and the visitor reading see the same information, with no second copy waiting to be synchronised. Keeping the admin panel and the published side in one application means the content is not held in two places.

  • Addresses and links

    Every page and every section carries a permanent address of its own, so a shared link always opens the same place. At Çatalca Merkez Kasap the menu is split into sections, and codes on different tables land on different points of the same page.

  • Access and permissions

    Who sees what, and who may change it, is defined together with the content type. At Vipkurum a teacher, a student, a parent and an administrator read the same lesson programme at their own level of permission.

  • An update is not a reprint

    When a price, a phone number or an address changes, the printed material stays as it is and the page is updated instead. Çatalca Merkez Kasap keeps its menu as text, so a price change never reaches the printer.

  • Repeat reads

    When the same page is opened again and again, it is served from a ready copy rather than rebuilt each time. QRVizit, still under development, opens a repeatedly scanned card that way.

Work like this

CMS · Case study

Kokudankokuya — the sellable unit sits under the product, price and stock on the volume

One choice carries the Kokudankokuya perfume catalogue: a scent is a single product record, and the volumes beneath it are the sellable units. Price and stock are held on that unit, so adding a size opens no second product in the catalogue and one size running out never closes the others. Alongside the category tree we put scent family and note as a second way through, letting a customer who knows no brand name start from character and arrive at an item. The catalogue's scale asked for no separate search or cache layer; the shop runs on Laravel and MySQL.

Read the case study →

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

  • One item comes in three sizes. Do we have to open three records?

    No — avoiding that is the point. The item stays one record and the sizes become sellable units under it. Description, images and category are held once, and all a size carries is its own price and its own stock.

  • If the panel gets complicated, the person at the counter will not use it. How much work is it?

    The measure is not how the panel looks but how far one correction spreads. Since price sits on the volume, changing a size's price is a single-field edit. Nothing has to be rewritten, and three records never need reconciling.

  • We are not in perfume. What does this shop say to us?

    It was built for perfume retail and we say so plainly. What carries is not the product but the level of the record: keep the sellable unit under the product and a size, a packing or a bundle stops opening a catalogue entry of its own. The name on the box changes; the arrangement holds.

  • We are a multi-branch business in Esenyurt. Would every branch see one catalogue?

    This shop was not built for several points, so we promise nothing here. Kokudankokuya is a single store, and branch transfers and till flow stayed outside it. Work where several institutions share one system is something we can only show through a different project.

CMS in other cities

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

Other services for this location

Let's talk about who will manage your content.

Get a quote or open the service