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

E-Commerce · Sariyer

E-Commerce for Sariyer businesses

A sales channel is rarely built from nothing. It is inherited: the people who wrote it have moved on, the documentation is thin, and the pages are still taking orders. In that position the first move is not writing but reading. If you hold an inherited channel in a head office on the Maslak tower line in Sariyer, the shape is familiar: the thing runs, and the risk of touching it is one nobody wants to own. We took over KGM SsangYong's corporate site in exactly that state and read the codebase before moving a line.

Get a quote Tell us about your project

E-Commerce — Sariyer

Sariyer's texture is the Maslak plaza line: technology and finance head offices, with the university campuses around Ayazaga nearby. If you inherited a sales channel, the issue is not scale but the handover itself: the team that built it moved on and the code stayed. The work closest to this district's profile is the KGM SsangYong corporate site. Where it does not overlap is worth saying plainly — that project is a corporate site rather than a store, and we have nothing to show there for baskets, payment or returns. What carries across is the order of work on inherited code: read it, leave what runs alone, keep the framework. Laravel, Tailwind, jQuery and MySQL stayed put; the Redis cache layer was the one addition.

  • Reading comes before editing on inherited code: which sections still hold and which ones carry the load is settled before anything moves.
  • The limit of the work is written down, so the parts that run are left where they are and the changes stay on what carries page weight.
  • Maintenance after the handover continues on the same tools — Laravel, Tailwind and jQuery stay put, and the framework itself does not change.

Why Algoriel

  • Priced by your own unit

    If you do not sell by the piece, the records do not either: Kokudankokuya prices and stocks every volume on its own.

  • Price moves with the choice

    Trim and colour update the price on the same screen, so a buyer never opens the basket just to see a total.

  • Used stock is a filter

    New and used machinery share one listing on Plastik ve Makina, with condition as a filter instead of a second catalogue.

  • One flow through to payment

    Configuring a product and paying for it are two steps of the same flow, with no handover to another system.

What we build

E-Commerce

  • The storefront

    The shop window, product pages, search and navigation follow how your customers actually look for what you sell. At Kokudankokuya the scent family and its notes open a second route beside the category tree.

  • Configuration into checkout

    When a sale needs choices and prices moving together, payment becomes the last step of that same flow rather than a separate form. On the KGM SsangYong sales channel the price updates on screen as the buyer picks trim and colour.

  • Variants and pricing

    Price and sales conditions attach to the unit you actually sell, so a customer never rebuilds a configuration at the next step. The KGM SsangYong sales channel stores every trim and colour pairing with its own price and its own image.

  • Inventory and operations

    Stock and order information is tracked the way your team already works. Kokudankokuya keeps a scent as one product record while each volume is its own sellable unit, so adding one never means opening another product.

  • Only the parts the job needs

    We do not assume your traffic and add layers for it, because you are the one who maintains them for years. Kokudankokuya's catalogue never reached a scale that called for a separate search layer.

  • Payment and shipping connections

    The payment and shipping providers you already use connect at the same point in the sales flow. You choose who you work with, and the connection is built around that choice.

Work like this

E-Commerce · Case study

KGM SsangYong corporate site — read the code first, keep the edits bounded

The site was already live: the job was to lighten what stood, not to build something new. The order was fixed: read the codebase, mark what works, confine changes to what carries page weight. Vehicle images moved into one naming and folder scheme, making visible which model calls which file. Catalog reads moved onto a Redis cache, so the same query stops running from scratch per visitor. Image sizes and jQuery requests on model pages were worked through one by one. Nothing arrived from outside the existing Laravel, Tailwind and jQuery set; the brand's side carries maintenance.

Read the case study →

Working with Sariyer 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 channel works but it is slow. Do we have to rewrite it?

    No. That is not how the SsangYong work started either. We read the codebase, left the working sections in place, and kept the changes on what carried the weight. A rewrite is not the alternative to taking a system over; it is the most expensive version of it.

  • The people who wrote our channel have left. Is that a problem for you?

    It is the starting condition, not a problem. On the site we took over, the source of truth was the code rather than any document. Nothing gets changed before it is read, and nothing ships before we can say which section touches what.

  • Do you have an office in Maslak, or could you sit with our team?

    Neither. We keep no office anywhere and the team works fully remotely. Taking over a system runs on reading the code, and sharing a floor does not make that reading faster. You get the limit of the work in writing: what was read, and where changes stopped.

  • Would you move us onto a newer framework?

    Not without a reason for it. On SsangYong we stayed inside the Laravel, Tailwind and jQuery set that was already there, and the one thing added was the cache layer. A dependency that changes the framework is weight for whoever inherits maintenance, and we do not pick a stack per project.

E-Commerce in other cities

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

Other services for this location

Let's plan your catalogue and your checkout.

Get a quote or open the service