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

Software Consulting · Sisli

Software Consulting for Sisli businesses

A catalogue that sells never closes. When the model has to change while the tills stay open, the question is not which platform to install but which record carries what. Cosmetics retail is dense around Tesvikiye in Sisli, and the same product can sit on the shelf in several sizes. Where an inherited catalogue has opened each size as its own product card, one price change is typed once per size. Kokudankokuya draws the line a level lower: price and stock ride on the volume.

Get a quote Tell us about your project

Software Consulting — Sisli

Sisli trades on the shop window, with cosmetics and perfume retail alongside central commerce. If your catalogue is edited often, consulting does not turn into a rewrite: a shop is already trading and the trouble lives in how its records are shaped. The work closest to this district's sector profile is Kokudankokuya. Where it does not overlap belongs on the page too: it was done for a perfume shop's catalogue model, and for in-store tills, resource planning or supplier integration we have nothing to show. What travels is where the sellable unit sits. The shop runs on Laravel and MySQL, so few parts need looking after.

  • When an inherited catalogue opens every bottle size as its own product card, one price change is typed once per size; moving the sellable unit onto the volume leaves a single record to edit.
  • Note and scent family open a second axis beside the category tree, so a buyer who does not know the brand starts from the character and still lands on a product.
  • The boundary belongs on the page as well: in-store tills, accounting transfer and marketplace connections fall outside this scope, and we have no work there to show.

Why Algoriel

  • We read the code first

    We did not build the KGM SsangYong corporate site; we read the inherited codebase and left the parts that worked untouched.

  • Fix where the load sits

    The same catalogue query hit MySQL on every page open; that read moved to a Redis cache and nothing else was disturbed.

  • We stay inside your framework

    On the KGM SsangYong site the inherited Laravel, Tailwind and jQuery set was kept; the cache layer was the one addition to the stack.

  • We reconnect broken chains

    At Resterm the calculation sat in a sheet, the catalogue in a file, the quote somewhere third; selection now runs to cart, project, and customer.

What we build

Software Consulting

  • Reading the code first

    We read the inherited codebase through, then name what moves and what stays untouched, one item at a time. The scope of the change comes out of that reading rather than a template.

  • Staying on the existing framework

    A library the maintaining team has never worked with would be a cost we left behind on our way out. KGM SsangYong's corporate site arrived with its framework and front-end libraries already chosen, and not one dependency was added to that set.

  • The limit of the change

    Only the slow places get opened; heavy spots are handled one at a time and the rest stays where it is. Where that limit falls is written down for you once the reading is done.

  • Tidying the file layout

    Scattered files move into a single naming and folder scheme. Which model uses which file becomes visible without reading code.

  • Taking weight off the reads

    The same query repeated for every visitor can be run once and shared from there. On KGM SsangYong's catalogue pages that query no longer runs until the data changes.

  • The decision taken before code

    Some decisions are made before the first line and are expensive to correct later. Resterm's software was built on the manufacturer's own product structure, because it was clear from the start that a general-purpose quoting tool would not carry it.

Work like this

Software Consulting · Case study

Kokudankokuya — in an inherited catalogue the sellable unit drops to the volume

A scent stays as one product record while the bottle volumes are separately sellable units: price and stock both ride on the volume. Adding a new volume opens no new product, and the scent record stays single. Note and scent family run as a second axis beside the category tree, and because a perfume can attach to more than one note, the same product turns up from different searches instead of sitting in one branch. The catalogue's scale asked for no separate search or cache layer, so the shop sits on Laravel and MySQL. Tills and accounting stay outside the scope.

Read the case study →

Working with Sisli 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 a shop that already trades and we do not want it rewritten. What does consulting do here?

    It starts by reading what runs: which information lives on which record, and where the sellable unit is held. Changes come afterwards and in pieces, so the parts that work are left alone. Dropping the sellable unit onto the volume in Kokudankokuya was one such decision.

  • Do we have to stop selling while the catalogue model changes?

    No. The window stays open through the day and the correction happens on the record side. Gathering product cards that were opened per size under a single scent does not interrupt trade; for the buyer the only difference is choosing the size on one page.

  • We sell cosmetics rather than perfume. What does this say to us?

    It speaks about the shape of the record, not the sector. On a shelf where the same product is sold in different weights the rule holds: the sellable unit drops under the product and carries price and stock. For campaign mechanics or a loyalty scheme we have nothing to show.

  • Did you build Kokudankokuya on your own?

    We did not. Kokudankokuya was built with a partner team alongside us, which is how we take on catalogue work without padding a headcount. We keep no office and the work runs remotely throughout. The first step is writing down which piece of information will live on which record.

Software Consulting in other cities

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

Other services for this location

Would you like us to read the system you already have?

Get a quote or open the service