Get a quote

Web Software · Sisli

Web Software for Sisli businesses

On a shop floor an adviser walks a customer through the options: this trim carries this price, that colour sells on those terms. Move the same walk onto a screen and describing is no longer enough — the page has to work the price out. If you are moving a brand's shop floor onto a screen around Nisantasi or Tesvikiye in Sisli, the knot sits at precisely that step. On the KGM SsangYong online sales channel, trim and colour choices build the price, and payment opens as the second step of the same flow.

Web Software — Sisli

Sisli's texture is the Nisantasi cosmetics trade and the central commerce around it, with brand windows and head offices in the same district. If all a page has to do is present, text and photographs cover it; the moment an option changes the price, presentation stops being enough. The work closest to this district's sector profile comes from automotive: the KGM SsangYong online sales channel. It was written for vehicles. In-store operations or stock across several shops are not work we can show, and we claim nothing there. What carries over is this: every trim and colour combination is stored with its own price, image and sales terms. The channel runs on the same Laravel, MySQL and Redis set as the brand's corporate site, with Tailwind and jQuery on the interface side.

  • The selection screen calculates rather than describes: change the trim or the colour and both the price and the pictured vehicle update at the same moment.
  • Price comes from the combination, since each trim and colour pairing is recorded with its own sales terms and that record is what moves to the next step.
  • Payment opens as a continuation of the configurator, so the visitor never leaves the vehicle they configured and never enters those choices a second time.

Why Algoriel

  • Brochure and requests together

    The pages that present your business and the screens that handle incoming requests sit in one application, as they do at Diotek.

  • Listings built on the server

    Product and stock listings are assembled on the server rather than in the browser, as they are on Plastik ve Makina.

  • A second way in

    A calculator, a filter or a listing page has an address of its own, so people arrive there straight from search.

  • Every page has an address

    On Günlük Hava Durumu every date and location keeps a permanent address of its own.

What we build

Web Software
  • A web application of your own

    The parts working behind the site are built around your own way of operating: incoming requests, approvals, lists, the admin panel. At Diotek a pre-sale site survey and a post-installation service call were built as two separate flows.

  • Pages rendered on the server

    Lists and pages are assembled on the server and arrive ready to display, so nobody watches an empty screen fill itself in. Plastik ve Makina refreshes its results in place when a filter changes, rather than reloading the page.

  • Performance and findability

    Every page carries a permanent address, and headings and content come out in a form a search engine can read. Günlük Hava Durumu publishes each date and location breakdown at its own address.

  • Validation on the server

    Form validation is never left to the browser; it happens again on the server. A request that arrives outside working hours still lands in writing instead of in a phone note.

  • Catalogue and filters

    A product, listing or content catalogue follows the distinctions your own trade makes, and the filters answer questions buyers actually ask. On Plastik ve Makina new and second-hand machines share one list, with condition as a filter.

  • Life after launch

    The team that writes the application also keeps maintaining it. Adding a section, or absorbing a busier season, does not mean standing up a second system.

Work like this

Web Software · Case study

KGM SsangYong online sales — configuration builds the price, payment continues it

KGM SsangYong sells its vehicles through an online channel of its own. A visitor picks a model and configures it through trim and colour, and each choice moves the price and the vehicle shown on screen at once. The price comes out of the chosen combination rather than a list row: every pairing is recorded with its own sales terms, and that record travels to the next step. Payment opens as the continuation of the configurator, so nothing is re-entered. The channel shares one Laravel, MySQL and Redis set with the corporate site. The context is automotive; what travels is how a choice builds a price.

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

  • Our options change the price. Can a catalogue page carry that?

    It cannot. A catalogue page shows a price, while here the choice constructs one. On SsangYong every trim and colour combination holds its own price, image and sales terms, and the screen reads from that record.

  • Did you build this on your own?

    No, the channel was a shared build. A job like this does not arrive in halves: the record carrying the price and the payment step reading it have to land together. You get one flow instead of an integration.

  • Our corporate site is one thing and sales sit somewhere else. What does joining them change?

    On SsangYong the sales channel and the corporate site run on the same Laravel, MySQL and Redis set. Maintenance is not split across two skill sets, and a configuration change is not repeated by hand in a second system.

  • Can a page do what the adviser on the floor does?

    The page carries the choice and the price. It does not carry persuasion, and we will not claim it does. The gain we describe is narrower: a visitor sees the price of the combination they built and moves to payment inside the same flow.

Let's work out what your site needs behind it.