Get a quote

ERP · Basaksehir

ERP for Basaksehir businesses

An ERP conversation usually starts at the order line. In a shop that builds to spec it cannot: at the order moment the product is not yet a catalogue item, because it is defined while the quote is written. The first link of the chain therefore falls on the sizing calculation. Machine build and tooling work is dense around Basaksehir's Ikitelli estate, and if your jobs come out to a measurement this is where manufacturing ERP has to start. Calculator Resterm sits exactly there: the buyer states a heating requirement rather than a product code, and the software works out which electric heater fits.

ERP — Basaksehir

Machine and equipment manufacturing sets the tone around Basaksehir's Ikitelli estate. Where a job comes out to a measurement and a specification, a fixed price list never carries it; with no ready code in a catalogue a quote line does not appear by itself, so someone runs the numbers and copies the result to the commercial side by hand. The work closest to how this district operates is Calculator Resterm. What sets it apart is where it was built: on Resterm's own product structure, so the calculation runs from inside it. Laravel runs the process, Vue draws the calculation screen and MySQL holds the records. Production scheduling, material requirements planning and cost accounting stay outside the evidence.

  • The product structure is the schema. A catalogue is not a list imported from outside; the calculation runs inside the maker's product logic, which is what turns a selection into a commercial line.
  • The software decides which heater fits, so a technical call stops queueing on one engineer's desk and the sales side can run the sizing.
  • A job is identified by its project record. Customer records and project records stay apart, so two jobs for the same buyer keep separate project files.

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

Calculator Resterm — the maker's product structure became the schema

Resterm manufactures electric heaters. Nobody hunts for a part number. The buyer states a heating requirement and the software returns the heater that fits. What mattered was where the software was built: a generic quoting tool carries a list, not the reasoning that says which product fits a case. We built this one on Resterm's own product structure and let the calculation work from inside it.

Read the case study →

Working with Basaksehir 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 have no fixed price list; every job is made to a measurement. How does software carry that?

    The product structure becomes the schema. We do not park a catalogue outside and import a list; the calculation runs inside the maker's product logic. Change the measurement and the same structure returns a different result.

  • Could we not load our catalogue into an off-the-shelf quoting tool?

    An off-the-shelf tool carries the list, not the reasoning that decides which product suits a case. The judgement stays with a person, so the quote still gets typed by hand. That is why Resterm's software sits on the manufacturer's product structure.

  • Is this an ERP, or a pre-sales tool?

    Our evidence covers the link between the technical selection and the commercial line. Production scheduling, material requirements planning and cost accounting sit outside it, and we do not promise a module we cannot show.

  • Our machine shop is in Basaksehir, on the Ikitelli estate. Would you not have to come and see it?

    No. We keep no office and we give no on-site support. What we need to understand is not the shop floor but how a heater is chosen from a given input, and that lives in the product structure.

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