Get a quote

E-Commerce · Fatih

E-Commerce for Fatih businesses

Between Tahtakale and Eminonu in Fatih the price list is still printed: right in the morning, out of date by late afternoon. If you are moving online, what you need first may be a list that stays current rather than a shop. The work nearest this district's trade profile is the QR menu we built for Çatalca Merkez Kasap. There a printed menu moved onto one page; when a price changes nothing is reprinted, the page is edited, and the same square code opens the current list.

E-Commerce — Fatih

Fatih's texture is historic peninsula retail: wholesale food, hardware and guesthouses. Whether you work by line count or by a list of rooms and services, keeping that list on paper makes the paper, not the catalogue, the thing that falls behind. That is what the Merkez Kasap job settled — the menu was split into sections, each section carries its own address, and different square codes land on different points of the same page. Where it does not overlap should be said plainly: that job is a menu with no ordering, payment or stock layer, so it is not what we point to when money has to be taken. Node.js runs behind it and Vue 3 shapes the page. We work entirely remotely.

  • The list is held as text, so a price change is an edit rather than a reprint and the same square code opens the current version.
  • Each section carries its own address: the code in the window lands on the hardware rows, the one at the counter on food, and nobody scrolls from the top.
  • The page loads once, so moving between sections opens no new request and the wait on a weak connection stays with that first load.

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

Çatalca Merkez Kasap — a QR menu whose sections are addressed separately

A single-page QR menu. The menu was split into sections and each section carries its own address, so different table or window codes land on different points of the same page. Share the link to a section and whoever opens it arrives at the same point, with no scrolling from the top. Built as one page with Vue 3, it loads once, and moving between sections opens no new page request, which keeps the wait on a weak connection to that first load. Because the menu is held as text, a price change is a page edit rather than a reprint. There is no ordering, payment or stock layer. Node.js runs behind it.

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

  • Our wholesale prices move often. How does this work without printing a new list each time?

    The list is held as text, so a price change updates the page and the same square code opens the current version. Printing drops out of the chain entirely. That is precisely what the Merkez Kasap job did.

  • The code in the window and the one at the counter open the same page. Is that not confusing?

    It is not, because each section carries its own address. The code stuck in the window lands on the hardware rows and the one at the counter on food, so nobody hunts for their section by scrolling.

  • Is this a shop? Could we take payment through it?

    That job is a menu: no ordering, no payment, no stock layer, and we say so plainly. If money has to be taken, the evidence to look at is a different project. What this page describes is a list that stays current.

  • Do you keep an address in Fatih?

    We hold no physical address and the whole job runs remotely. First we write down which line belongs in which section, then development begins.

Let's plan your catalogue and your checkout.