Get a quote

E-Commerce · Atasehir

E-Commerce for Atasehir businesses

A group with several brands is not really asking how to build one shop. If you run several brands from a head office on the West Atasehir tower line, two wishes meet head on: every brand should appear on its own address, and no second installation should turn up to be looked after. That tension usually gets closed with a brand filter dropped onto the screen. Vipkurum, the work closest to how companies here are put together, draws the line at the door instead.

E-Commerce — Atasehir

What defines Atasehir is not a sector but a shape: the decision sits in the centre, several brands under it, each keeping its own customer list. Vipkurum was built for that shape. Seven education institutions run one system, each on its own domain and brand, and an institution's student, guardian and payment records stay inside its own edge. Where it does not overlap: Vipkurum is not a shop. Payment there means collecting fees, and we have no basket, shipping or marketplace connection to show. What travels is where the edge is drawn. Underneath sit a Laravel core, MySQL and MongoDB records and a Redis cache, React on the panel, React Native (Expo) on mobile. We have no finance client and work fully remotely.

  • Every brand arrives on its own address: in Vipkurum one school's student, guardian and payment records never open to the institution next door, and the split is not left to a filter added later.
  • Bringing a brand under the roof defines a new organisation rather than opening another installation, so a second brand does not start a second maintenance line.
  • An institution defines its own content and its own assessment type from the panel, so a new criterion waits on no release from us.

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: seven institutions in one system, each with its own domain and brand

Seven education institutions run one system under their own domains and brands. The separation sits at domain level: a school's student, guardian and payment records are invisible to the next. Timetables, exams, payments and reporting share one platform, and reports are drawn from the administrator's own organisation's data. An institution defines its own assessment type in the content management layer, so a new criterion waits on no code change. React drives the panel and React Native (Expo) mobile, both on one Laravel core; MySQL and MongoDB hold records, Redis the cache. The boundary: a school platform, not a retail basket.

Read the case study →

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

  • We run several brands. Does each one need its own installation?

    No. Seven institutions sit in one system in Vipkurum, and each arrives on its own domain. Adding a brand defines a new organisation rather than opening an installation, and the upkeep stays in one place.

  • Vipkurum is a school platform. What does it say about our storefront?

    We say it is a school platform and leave it at that. Payment there is fee collection, and we have no basket, shipping or marketplace connection to show. What it does say is where the edge belongs: the institution arrives on its own address and its records stay behind that address.

  • Can one of our brands set up its own campaign without us?

    In Vipkurum an institution builds its own lessons, tests and exams from its panel, and because it defines the assessment type itself, a new criterion waits on no release from us. The measure would be the same for you: during scoping we write down which decisions stay in the panel.

  • Why not open one shop and separate the brands with a filter?

    You can, but then the edge lives inside the query. In Vipkurum the edge sits at the door: an institution arrives on its own domain and its record set begins there. A filter can be forgotten; a domain cannot. For a group run from one head office, that difference decides whether one brand's customer list can appear on another brand's screen.

Let's plan your catalogue and your checkout.