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

ERP · Bakirkoy

ERP for Bakirkoy businesses

Is the thing on the shelf one product or several? Bakirkoy's retail line runs along Incirli and Atakoy; sell the same item in bottles or packs of different sizes and the stock count jams right there, because the identity is single while the sellable unit is not. The question ERP software in Bakirkoy, Istanbul has to answer is which level stock is held at. At Kokudankokuya a scent stays one product record while the volumes stand as separate sellable units.

Get a quote Tell us about your project

ERP — Bakirkoy

Bakirkoy's retail line on the western side of the city is busy, and a cosmetics, fragrance or personal care shelf holding one item in several sizes is an ordinary arrangement. The district also holds a dense cluster of private healthcare providers, which is a different fabric and not where our evidence sits — we have nothing at hospital or chain-clinic scale. On the retail side the closest work is Kokudankokuya. What it does not cover, said plainly: the store carries the selling side, and production planning, supply chain, consolidated finance and human resources fall outside. The scope holds at the operations record, stock movement and the accounting side. Laravel and MySQL carry the store; no separate search or cache layer was needed.

  • Stock and price are tracked at the sellable unit, meaning the volume, while the scent itself remains one product record in the catalogue.
  • Scent family and note open a second way through the catalogue beside the category tree, so a shopper who does not know the brand starts from character and arrives at a product.
  • The number of moving parts was kept low deliberately: the scale of this catalogue called for no separate search engine and no cache layer.

Why Algoriel

  • Work order through to invoice

    In AlgoCar information is entered once and carried on the same record from the work order to the invoice.

  • Stock moves next to the job

    Parts leave stock against a work order, so nobody hunts for where a part went at month end.

  • The calculation becomes the quote

    Resterm sizes a unit with an engineering calculation, and the result drops into the cart and the project record.

  • Where the scope stops

    Operations, stock and accounting are in scope. Production planning, supply chain, consolidated finance and HR are not.

What we build

ERP

  • Work order, part and invoice on one chain

    At AlgoCar a work order opens, the part consumed is written to it, and the invoice comes from that same record. The chain never splits across three programs.

  • The same movement is never typed twice

    A part leaves stock the moment it is written to the work order. No warehouse screen sits waiting for the same consumption to be keyed in again.

  • Cost and revenue in one system

    The trading and accounting side runs in the same system as the service record, so the two faces of a job are not reconciled after the fact.

  • Spend that accumulates on the asset

    At AlgoCar servicing and repair build up under the plate and chassis record, so what a vehicle has cost in total is read from its own file.

  • Where a quote line came from

    At Resterm you can trace a quote line back to the heating requirement that produced it.

  • From calculation to basket to project

    The product the engineering calculation selects drops into the basket, the basket attaches to a project, and the project to its customer. The records stay on one chain.

Work like this

ERP · Case study

Kokudankokuya — identity on one product record, counting at the sellable unit

In perfume retail a scent is one product record while the volumes are separate sellable units. The split has a practical result: counting and pricing run at volume level, yet the identity in the catalogue stays on a single record, so one scent never multiplies down a list. A second axis runs alongside it — scent family and note open their own path beside the category tree, and because a perfume can hang off more than one note it turns up under different search intents. The stack was kept narrow: Laravel and MySQL carry the store, with no separate search or cache layer.

Read the case study →

Working with Bakirkoy 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 sell the same item in several sizes. Does each size need its own product record?

    It does not have to. In Kokudankokuya the identity and the sellable unit sit on two levels: the scent is one record, the volume is a separate unit. Counting and pricing run at the unit; listing stays on the record.

  • Have you worked with healthcare providers in Bakirkoy?

    No. We have nothing at hospital or chain-clinic scale, and we do not build sentences on a reference that does not exist. What this page draws on is the resemblance between the district's retail line and how Kokudankokuya shapes its records.

  • How does a shopper find a product without knowing the brand?

    The catalogue carries a second way through it: scent family and note. The shopper starts from character and arrives at the product. Because one perfume can attach to several notes, it is never locked into a single category branch.

  • Do you also build warehouse transfers and purchasing?

    We do not. Our evidence stops on the selling side of the store. Warehouse transfers, supply chain, production planning and consolidated finance are outside this scope, and we do not promise a module we cannot show.

ERP in other cities

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

Other services for this location

Is the cost of a job still meeting its revenue at month end?

Get a quote or open the service