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

CMS for Fatih businesses

In Fatih's han floors between Vefa and Unkapani a shop can have no window at all: the goods sit upstairs, out of sight from the street. With nothing to point at, a buyer assembles what they want in conversation, and that assembly gets written down twice: once on a pad, then again on the invoice. In a business like that the screen becomes the only display surface there is. On the KGM SsangYong online store, configuring and paying were built as two steps of one flow.

Get a quote Tell us about your project

CMS — Fatih

On Fatih's wholesale side what gets sold is rarely sitting finished on a shelf. Quantity, packing and extra work are settled as the conversation runs, and the figure arrives last. In a shop invisible from the street, the screen is the only place that assembly ever becomes visible. The work closest to this district's sector profile is the KGM SsangYong online store. The evidence stops here: the channel was written for an automotive brand, and wholesale ledgers, room inventory and hardware stock counts are not things we can show. What we describe is narrow — a configuration becoming a record, and that record carrying into payment. Laravel, Tailwind, jQuery, MySQL and Redis sit underneath.

  • Every trim and colour combination is recorded with its own price, its own image and its own sales condition, so on the content side it is a record rather than a line in a description.
  • Payment opens as the continuation of the configurator: the settled configuration carries into the next step and nothing the visitor chose is typed a second time.
  • The sales channel runs on the same Laravel, MySQL and Redis set as the brand's corporate site, keeping the upkeep of both inside one skill set.

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

KGM SsangYong online store — the configuration settles, payment inherits the record

A vehicle sales channel running from configurator to payment. A visitor picks a model, then builds it up through trim and colour, and each choice moves the price and the image at once. The price comes out of the chosen combination, and every combination is recorded with its own sales condition. Payment opens as the continuation of that flow: the settled record carries forward, so the visitor buys without leaving the vehicle they configured. The channel shares a Laravel, MySQL and Redis set with the corporate site. Scope is vehicle sales; ledgers and stock counts sit outside.

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 have no ready product pages — the price comes out of a conversation. What use is this channel?

    That is precisely the part we describe. If a price comes out of a conversation, the outcome of that conversation is not becoming a record: the figure on the pad and the figure on the invoice are written separately. Here the choice is the record, and payment inherits it, so no second writing step exists.

  • Would we have to open a page for every combination?

    No. A combination is a record, not a page: its price, its image and its sales condition sit in that record's own fields. What gets managed on the content side is the options themselves rather than a text written out for every possibility.

  • We run a guesthouse in Fatih. Would this work for rooms and service items?

    The channel was written for an automotive brand, and room inventory and channel management were never built into it — we have nothing to show there. What carries is the shape of the chain: a choice becomes a record and payment takes that record. Rename the item and the number of steps stays the same.

  • Do we update what is on screen, or do we call you?

    Options and sales conditions are managed on the business side, so a change to one trim's price stays inside that record. We keep no office and the work runs remotely.

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