Get a quote

ERP · Esenyurt

ERP for Esenyurt businesses

Esenyurt is thick with small businesses, and a shop around Mehtercesme or Talatpasa that publishes its own product or service list has one decision to make: where the list is built. Build it only in the browser and the result turns odd — a customer sees a page, a search engine an empty shell. At Plastik ve Makina we prepared the list on the server. Laravel assembles it and Inertia carries it to the browser; changing a filter reloads nothing, yet a listing's content still arrives inside the server's response. For a firm with several branches that difference decides whether the list is found at all.

ERP — Esenyurt

Esenyurt's small business and private education fabric is spread over many points, and one name running from several branches — or each branch publishing its own enrolment page — is nothing unusual. The work closest to how this district operates is Plastik ve Makina. Where it does not overlap, first: it is a sector listing platform for people buying and selling plastics processing machinery, so no branch management, no course enrolment and no stock count was built there, and we have nothing on the warehouse or transport side either. What travels is where the list is produced. Laravel carries the application, Inertia takes the interface to the browser, MySQL holds the listing records, Redis takes the cache and Tailwind shapes the screens. Consolidated finance, human resources, production planning and the supply chain are not on this list.

  • The list is assembled on the server, so the content of a listing page arrives in the response without the browser having to ask again.
  • Changing a filter refreshes results in place rather than reloading the page, so nobody loses the list they were reading.
  • Our scope is the operations record, stock movement and accounting; production planning and human resources are areas we have nothing to show for.

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

Plastik ve Makina — the list is built on the server, the listing arrives in the response

A sector listing platform we built for the people who buy and sell plastics processing machinery. What this page rests on is how the list is produced: Laravel prepares it on the server and Inertia carries it to the browser. That cuts both ways. A buyer changing a filter gets no full page reload — results refresh in place. And because a listing's content arrives inside the server's response, the page does not present itself to the outside as an empty shell. MySQL holds the listing records, Redis takes the cache, Tailwind shapes the list and detail screens. Stock counting, purchasing and accounting were never built in this platform.

Read the case study →

Working with Esenyurt 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 list is on the site but never shows up in search. What could be wrong?

    Usually it comes down to where the list is assembled. If it is produced in the browser, the first response for that page arrives empty: the customer sees results, an outside reader does not. At Plastik ve Makina we prepared the list on the server, so the content is in the response itself.

  • We are a multi-branch business in Esenyurt and each branch keeps its own list. How does that get pulled together?

    Vipkurum is the evidence: seven institutions there share one system, each with its own domain and brand. Branches appear on separate pages while the record is kept in one place — the structure is shared, the visible face is not.

  • Is this an ERP? Does it cover the warehouse and dispatch side?

    There is no warehouse or dispatch here — we have no logistics work in the portfolio, and we do not promise evidence we lack. On the ERP side what we describe is the operations record, stock movement and accounting; production planning, the supply chain, consolidated finance and human resources sit outside that.

  • We already have a working site and would rather not throw it away.

    You may not have to. We start by looking at where the list is produced; the trouble is often not the design but content that never enters the response. On the SsangYong corporate site we did not start over either — we took the existing system on, improved it and reorganised the storage layer.

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