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

E-Commerce for Sisli businesses

At a perfume counter the order is fixed: you smell first, then settle the bottle size at the till. Online that order can invert — with nothing to test, a shopper picks a size before knowing the scent. So the first question is a catalogue one: is the sellable unit the scent, or each bottle size? Kokudankokuya, the work closest to this district's retail profile, answers it underneath the product.

Get a quote Tell us about your project

E-Commerce — Sisli

Sisli's texture is the Nisantasi cosmetics trade and the central commerce running between Tesvikiye and Mecidiyekoy. If you sell one product in two sizes, the catalogue decision lands here: give each size its own record and the listing fills with the same name, or fold them together and it stops being visible which size sold and what is left. Kokudankokuya resolves this below the product: a scent is one catalogue record, each bottle size a unit carrying its own price and stock. The store runs on Laravel with MySQL. We work fully remotely.

  • Size is chosen after the scent: since the scent is one record, a shopper switches size without leaving the page, and the price shown belongs to that size.
  • Selling out belongs to the size, not the scent — stock is held at size level, so one bottle running dry leaves the scent listed.
  • A scent's character is kept as a link rather than a line of prose, so one perfume attaches to several notes and surfaces under different filters.

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

Kokudankokuya — a catalogue that carries the decision with nothing to smell

A perfume buyer commits without smelling anything, and part of what sells is a gift, not a purchase for the buyer. The catalogue has to hold both. We put the model underneath the product: one record per scent, price and stock attached to the bottle size. Size becomes a pricing decision taken after the scent, and one size selling out leaves the scent listed. Notes are stored as links, so a perfume is reachable from several of them. The store was written in Laravel, and the catalogue lives in MySQL.

Read the case study →

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

  • Customers buy without smelling anything. How does the catalogue handle that?

    It narrows the field rather than closing the gap. No catalogue stands in for the tester itself, and we say so plainly. Because a note is held as a link it works as a filter: a shopper starts from a character they know and shortens the list before deciding.

  • One bottle size sells out. What happens to the product page?

    It stays where it is. Stock sits on the size rather than the scent record, so what runs out is that single size; the scent keeps its place and the remaining sizes stay buyable.

  • A share of our sales are gifts. Does that change the model?

    It changes the order, not the model. Whoever buys a gift will not wear the fragrance, so the shortlist forms around the character of the scent, and size turns into a price decision rather than a question of longevity.

  • Who built this, and how would you work with us?

    We did not. Kokudankokuya was built together with another software team. With you the first question sits on your own listing: where price and stock are held, and whether one product is repeated once per size. Your answer to that is what the catalogue gets built on.

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