Get a quote

E-Commerce · Istanbul

E-Commerce for Istanbul businesses

In Istanbul's higher-value retail, what a customer buys is often the result of a choice rather than a shelf item. Off-the-shelf cart software prices a single catalog row and stops there, while every trim and color combination carries its own price, its own image and its own sale terms. The work closest to this city's commercial profile is the KGM SsangYong online store, where the configurator and the checkout are two steps of one flow.

E-Commerce — Istanbul

Istanbul carries the country's heaviest commercial traffic, and a brand can run a sales channel of its own next to the marketplaces it already sells on. The real cost of that second channel shows up not in the build but as a second system to maintain. On the SsangYong work we kept both inside one skill set: the store runs on the same Laravel, MySQL and Redis set as the brand's corporate site, and the two sit in one maintenance routine. We choose a stack we can still maintain years later, and we keep it across projects.

  • Every trim and color combination is stored with its own price, its own image and its own sale terms.
  • Price and image update on the same screen as the buyer changes the configuration.
  • Checkout opens as the next step of the configurator, so the specification carries over and nothing is entered a second time.

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

KGM SsangYong Online Store — configurator and checkout as two steps of one flow

What is sold here is not a stock item but the result of a configuration: every trim and color combination carries its own price, its own image and its own sale terms, and off-the-shelf carts do not hold that breakdown. Price and image update on the same screen as the visitor changes the configuration, and checkout opens as the continuation of the configurator — the selection stays in the same session, so nobody builds the car a second time. The sales channel is maintained on the same Laravel, MySQL and Redis set as the brand's corporate site.

Read the case study →

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

  • How does a remote agency work with an Istanbul brand?

    We have no office and the whole team works remotely. What we need from a brand is its current sales flow: how a price is agreed today and who signs it off. The SsangYong store puts the configuration in the buyer's hands, and the price follows the choice. Your sales flow is where we would start too.

  • Will it hold up during heavy campaign traffic?

    We do not quote load figures, because we have not measured them. What we can describe is the mechanism: on this brand's corporate site we moved catalog reads onto a Redis cache, so the same query stops hitting MySQL on every page view. The store runs on that same Laravel, MySQL and Redis set.

  • Can checkout sit inside our own sales flow?

    At SsangYong, payment opens as the next step of the configurator — the buyer moves into purchase without leaving the specification, and the selection stays in the same session. That is where we would start on your flow too: no gap between the screen where the choice is made and the screen where it is paid for.

  • What happens to the store we already run?

    Taking over a working system is the job we have done: on this brand's corporate site we read the existing codebase first, left the working parts alone, and kept the framework that was already there. A running store would follow the same order — read it first, then touch only what carries the page load.

Let's plan your catalogue and your checkout.