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

E-Commerce for Esenyurt businesses

When what lands in the basket is an hour rather than a box, a stock catalogue stalls at the first step: a product record counts units, it does not count duration. In a branch-run small business or a private course room along the Kirac stretch in Esenyurt, the same service can take longer in one room than in another, while the basket still sees a single line. AlgoRandevu, the product we are building right now, starts from that gap.

Get a quote Tell us about your project

E-Commerce — Esenyurt

Esenyurt's texture is dense small business and private education, much of it along the Kirac stretch. If one name runs several rooms, each room has its own resource. Once selling moves online, the question stops being how the product page looks and becomes which resource the sold hour is written against. The work standing closest to how businesses run here is AlgoRandevu — our own product, still under construction, and we do not present it as a finished install. Where it does not overlap is plain too: it is a booking product, not a shop carrying shipping and returns, and shelf trade is not what it demonstrates. Underneath sit a Laravel core, MySQL records and a Redis cache, with Inertia and Tailwind on the interface.

  • The unit sold is a span of time: its length and the gap before the next one live in a product setting, so no sector-specific build has to exist.
  • A booking can attach to a person, a room or a piece of equipment, so one branch picks its own resource while the same service opens differently in the next room.
  • We are building it on the Laravel and Inertia footing that already carries AlgoKlima and AlgoCar, so a business already running one of those panels meets familiar screen logic.

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

AlgoRandevu — booking length and resource live in a setting, not in the code

Our own product, still under construction rather than a finished install. Instead of baking the length of a booking, what it attaches to and how bookings queue behind one another into a sector, we leave all three definable inside the product: when a rule changes, a setting changes and the code stays put. In the shape we are working on, a booking attaches to a person, a room or a piece of equipment, so a business picks its own resource and we write no separate flow per sector. Bookings are held in MySQL, Redis sits as the cache layer and Tailwind shapes the panel, on the same Laravel and Inertia footing as AlgoKlima and AlgoCar.

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

  • What we would sell online is a session, not a product. Why does a standard basket fall short?

    A standard basket counts units and carries neither the length of a session nor what that length occupies. Selling an hour means the record has to hold two things: how long the span runs, and which resource it ties up. In AlgoRandevu both sit as product settings.

  • Our branches run the same service at different lengths. Can that live in one product?

    It can, because the length is written to the product setting rather than to the name of the service. Each branch picks its own span and its own resource, and no separate build has to be cut per room.

  • Could we install AlgoRandevu today?

    No. We are still building it and will not describe it as finished. What we can work on today is the flow itself: which resource a booking attaches to and where its length is defined. Development starts once that is written down.

  • Do you have anyone based in Esenyurt?

    We keep no office and run the work entirely remotely. The first step is text rather than code: we set out together which piece of information belongs in which record.

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