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

ERP for Catalca businesses

In a shop in the centre of Catalca the counter can be in one place and the back office in another, with whoever follows the work moving between them. Buying three programs for three surfaces means typing the same thing three times. Tahlil.com was built the other way round: the website, the admin panel and the phone app all hang off one Laravel application, and when the state of a record changes the app says so itself.

Get a quote Tell us about your project

ERP — Catalca

Trade in Catalca runs through food retail and town-centre shops, and even a small business can end up working across three surfaces: the counter, the back office, and letting someone know. The one genuine local tie in this network sits here: Merkez Kasap's QR menu is live in Catalca, but that is a menu page, not an ERP. The work this page rests on is Tahlil.com, with no tie to Catalca; what comes close is the shape it was built in. Where it does not overlap is plain: a health platform with no stock, till or accounting. Laravel carries the application, MySQL the records, Redis the cache, Tailwind the interfaces; the mobile side is React Native (Expo), with OneSignal for the push. Supply chain, production planning, human resources and consolidated finance stay outside.

  • The same Laravel application sits behind all three surfaces, so a record changed on one of them is already current on the next.
  • Letting someone know is not left to a person: once the state of a record changes, OneSignal pushes the notification to the phone.
  • On the ERP side what we promise is the operations record, stock movement and accounting; production planning, the supply chain and human resources fall outside it.

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

Tahlil.com — three surfaces on one Laravel application, the push comes off the record

A patient enters test values; a specialist doctor writes and approves the comment in the panel, so the final wording is the doctor's. What this page rests on is the structure: the site where values go in, the panel where the comment is written and the patient's app all attach to one Laravel application, and the app keeps no copy of the data. Once a comment is approved, telling the patient is nobody's task: OneSignal pushes it. MySQL keeps the records, Redis the cache, Tailwind the interfaces; the mobile side is React Native (Expo). Stock, till and accounting were never built here.

Read the case study →

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

  • Is the Merkez Kasap QR menu in Catalca actually your work?

    It is. It is the one genuine local tie in this network and we do not hide it, but we do not inflate its scope either. It is a page that took the place of a printed menu; there is no stock, no till and no accounting in it. On the ERP side the work we rest on is Tahlil.com.

  • We are a small business. Do we really need a site, a panel and an app?

    You do not need all three, but if a second one is coming later, the first decision matters. At Tahlil.com the surfaces are not separate systems; they are the visible sides of one application, so adding another does not mean setting the data up a second time.

  • Is this an ERP? Where are stock and accounting?

    Not in Tahlil.com, and we say so. On the ERP side our promise stops at the operations record, stock movement and accounting, while the evidence on this page shows the structural half of that promise: several surfaces attached to one record. Production planning, the supply chain, consolidated finance and human resources are promised on none of our pages.

  • You did the work for Merkez Kasap. Could you look at ours as closely?

    We could, but closeness does not come from geography. We keep no office and the work runs remotely; at Merkez Kasap what brought the work close was writing down how the menu would be put together. We use the same method for the counter and the back office.

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