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

Enterprise & Commercial Software · Pendik

Enterprise & Commercial Software for Pendik businesses

When two sales points quote two different figures for one product, the price list is not the problem. Where the price is read from is. Kaynarca and Velibaba in Pendik sit on a line of manufacturing SMEs and multi-point service organisations. Add options and a price list stops holding. On the KGM SsangYong sales channel a price is never looked up on a row. Trim and colour choices build it, and the chosen pairing resolves into one record that carries its sales terms with it.

Get a quote Tell us about your project

Enterprise & Commercial Software — Pendik

In Pendik's manufacturing fabric a product can be described from more than one desk: a dealer, a service point and the head office. If each desk reads the price from its own copy, the figure drifts between them. The KGM SsangYong online sales channel is the nearest thing we have to that picture. Where it does not overlap is worth saying: the channel was written for automotive retail, so a manufacturer's production plan, machine schedule and service work orders sit outside it. What travels is which record a price sits on. The channel runs on Laravel, Tailwind, jQuery, MySQL and Redis.

  • A price is not read off a list row but worked out from the selection, and every trim and colour pairing carries its own figure and its own picture.
  • The payment step never asks for the selection again: the configured vehicle moves across as a record, so both steps read one line.
  • The sales channel shares a technology set with the brand's corporate site, which keeps maintenance inside one area of skill instead of opening a second.

Why Algoriel

  • Many institutions, one system

    Vipkurum runs seven institutions on the same system while each one keeps its records to itself.

  • Adding one adds a boundary

    Each Vipkurum institution signs in at its own domain under its own brand, so adding one does not mean a second installation.

  • Each branch runs its own work

    A branch marks its own exam sheets, so one broken device does not stall every institution at once.

  • Each role, its own view

    Timetable, exams, students, parents, payments and reporting sit on one platform, and who can see what is settled up front.

What we build

Enterprise & Commercial Software

  • Each institution signs in through its own domain

    At Vipkurum, seven education institutions open under their own address and their own brand, and the name of the software never appears on a user's screen.

  • No reinstallation for a new institution

    Adding one more institution means writing a definition. No second copy of the system is stood up, and the maintenance stays in one place.

  • Office and field on the same record

    AlgoKlima's office panel and field app read and write the same record. A technician closes the job where there is no signal, and the entry reaches the office panel once the connection returns.

  • Operational and commercial records close together

    At AlgoCar the service record and the commercial record sit in the same system, so the cost of a job and its revenue are not reconciled across two programs.

  • One institution's data stays closed to the next

    Student, parent and payment records stay inside the boundary of the institution they belong to. That boundary is how the system is set up, not a view switched off on a screen.

  • One technical footing we can maintain for years

    Nothing goes into your system that the team maintaining it does not already know. AlgoKlima and AlgoCar are our own products, built on that same footing, and we work on it every day.

Work like this

Enterprise & Commercial Software · Case study

KGM SsangYong Online Store — price worked out from the pairing, record carried to payment

A sales channel for KGM SsangYong vehicles. A visitor picks a model, then builds it through trim and colour; the price is worked out from that selection while the vehicle shown changes with it. Each pairing resolves into a record carrying its own figure, its own picture and its own sales terms. Payment takes that record over, so the buyer never leaves the vehicle they built or enters those choices twice. The channel shares its Laravel, MySQL and Redis set with the brand's corporate site, with Tailwind and jQuery on the interface side. Context: automotive retail.

Read the case study →

Working with Pendik 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 option count keeps growing and the price list no longer holds. What stands in its place?

    The pairing itself. A price stops being a row to look up and becomes a result worked out from the selection, with every trim and colour pairing recorded under its own sales terms. A rule is updated instead of a list.

  • Our dealer and our service point quote from separate desks. How do you tie that to one place?

    By leaving one place to do the arithmetic. As points multiply, what multiplies is the screen rather than the calculation, and everyone reads the same record. We keep no office and run this remotely, so nobody travels to install anything.

  • We are in machinery, not automotive. What does this channel say to us?

    The channel was written for automotive retail and we say so plainly. What carries across is which record a price comes from: attach the options to a record rather than a document, and the sales point and the production side read the same figure.

  • Who built the channel? Did you work on it alone?

    We did not work on it alone. The KGM SsangYong sales channel was built with a partner firm, so the pricing rules were never held by one person alone. When someone is away and a figure has to change, your side is not waiting.

Enterprise & Commercial Software in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

How many institutions and branches should we plan your system around?

Get a quote or open the service