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

E-Commerce for Kadikoy businesses

A checkout line that reads as one item tells the buyer almost nothing. In a consulting room along Bahariye in Kadikoy or a studio nearby, what sells may not be a single item at all but a programme assembled from parts. The work closest to how service businesses here sell is a CRM we built for a dental clinic. There the plan counts every tooth as its own line, what will be done and where is written out one by one, and only then does the order break into sessions.

Get a quote Tell us about your project

E-Commerce — Kadikoy

Kadikoy's texture is service businesses that run by appointment: consulting rooms, studios and small retail around Caferaga and Bahariye. If your online side stops at a contact form, the real record stays indoors. The pinch comes from what sells being assembled: the programme differs per person and will not list as a fixed-price shelf item. In the dental clinic CRM we settled the shape of that record — the plan stands on its own and can be read before a single hour has been set aside. What does not carry across is plain: that job is not a shop, it has no basket and takes no payment online, and what travels is not a storefront but the way a sellable thing is built out of lines. Laravel runs the process and MySQL holds the plan and invoice records.

  • What sells is assembled from lines: the record holds which procedure goes where, one by one, and the amount comes off those lines.
  • The programme is a record independent of the calendar, so a buyer can read what was bought line by line before any hour is set aside.
  • Payment is taken once while delivery spreads over sessions, and which line is done and which is still waiting come off the same record.

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

Dental clinic CRM — the programme is built line by line, delivery runs by session

What a clinic sells is not a single-line service but a programme assembled per person. The plan counts every tooth as its own line: what will be done and where is written out one by one, and the amount comes off those lines. The plan is a record in its own right, readable before any hour is set aside, and the order breaks into sessions afterwards. Payment is taken once while delivery spreads over weeks, and which line is done and which is still waiting come off the same record. It is not a shop: no basket, no online payment. Laravel runs the process and MySQL holds the plan and invoice records.

Read the case study →

Working with Kadikoy 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 sell is not a fixed-price product but a programme assembled per person. How does that sit in a catalogue?

    Not as a single line. The programme is built from lines: which procedure goes where is written out one by one, and the amount comes off those lines. In the dental clinic CRM the record holds exactly that shape.

  • Taking payment up front while delivery spreads over weeks — does that muddle the record?

    It does not, because the sale and the delivery are two faces of one record. A buyer sees which line is done and which is still waiting from the same place, and no second ledger opens.

  • A dental clinic CRM is not a shop. What does it tell us?

    Let us name what it does not do: no basket, no online payment. What carries across is not a storefront but the way a sellable thing is built out of lines. We keep no office and the working model was remote from the start, so this distinction goes down in writing before anything is built.

  • We run a studio and sell fixed packages rather than assembled programmes. Does the same record help?

    If what you sell does not change per customer, the line structure earns nothing; a fixed package sits in a plainer record. Lines start paying off only once the programme is composed per person.

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