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

E-Commerce for Uskudar businesses

When several institutions share one roof, selling is the first thing that cracks. Each wants to take money under its own name, yet payments and enrolment records collect in a single pool, and one administrator ends up reading the row next door. If an education or service institution around the Altunizade stretch in Uskudar sits under a roof like that, this is where the question comes from. On Vipkurum the line is not drawn in the interface at all: the separation lives in the database schema and is set at domain level, with seven institutions running one system from their own addresses.

Get a quote Tell us about your project

E-Commerce — Uskudar

Institutional density in Uskudar comes from services: course centres, private clinics, studios, consultancy offices. If a few names sit under one roof, each name wants to collect payment as itself. The work closest to this district's profile is Vipkurum. Where it does not overlap is plain: that is a management platform for education institutions, not a retail store, and we have nothing to show for physical goods, shipping or returns. What carries across is where the line gets drawn: the separation is a schema decision rather than an interface one, and the records an institution reads stop at its own edge. One Laravel core carries a React panel and a React Native (Expo) mobile side, with MySQL, MongoDB and Redis behind it.

  • The line sits in the database schema instead of the interface, so one institution's student, parent and payment records never appear in a neighbour's panel.
  • An institution defines its own assessment type, which lets European and Turkish criteria sit on one infrastructure without waiting for a code change.
  • Adding an institution to the roof defines a new organisation rather than opening a fresh installation, and invoicing, payment and analysis reports come off that institution's own data.

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

Vipkurum: the boundary lives in the schema, set at domain level

Seven education institutions sit under one roof, each entering from its own domain under its own name, one system turning underneath. The line is not in the interface: student, parent, payment and invoice records stay inside the institution, never surfacing in a neighbour's panel. Timetables, classes, branches and exams sit in one data model, reached only as far as a role's permission goes. An institution defines its own assessment type, so a new criterion needs no code change. One Laravel core carries the React panel and the React Native (Expo) mobile side; MySQL and MongoDB hold records, Redis the cache.

Read the case study →

Working with Uskudar 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

  • Does each institution collect payment under its own name, or is there a shared storefront?

    Under its own name. The institution enters from its own domain, a visitor sees that institution's brand, and one system turns underneath. What is shared is the infrastructure; what separates is the boundary of records each institution can reach.

  • Could an administrator accidentally read another institution's payment record?

    Because the line sits in the schema, this is not a matter of hiding a screen. The institution enters from its own domain and the query ends at that institution's edge, so another institution's row never enters the result set at all.

  • Does adding a new institution mean a second installation?

    No. An institution joins the roof as a new organisation definition; the system is not copied and the institution's record side starts empty. Because there is one maintenance line, a single fix reaches every institution at once.

  • Would you not need to visit our institution in Uskudar and watch the process?

    We would not. We keep no physical office and the working method is remote from the start. Enrolment records and permission boundaries get settled by writing out the permission matrix row by row rather than by a visit, which is how the Vipkurum work ran too.

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