Get a quote

ERP · Beylikduzu

ERP for Beylikduzu businesses

Beylikduzu is thick with showrooms and sales floors, and on a sales floor the door belongs to the customer: a turnstile takes up room and has to come out again when the point closes. If the same person works on more than one floor in a week it gets harder still. The construction workforce app was built for that condition: we put no device at the door. A worker scans a code from their phone, and the place where the scan happens decides which point the record belongs to.

ERP — Beylikduzu

In Beylikduzu the product meets the buyer on a display stand or a screen. Where a business does not stay at one address and spreads the same team across several points, the attendance record has to travel from point to point with them. The work closest to how this district operates is our construction workforce attendance work. Where it does not overlap goes first: it was written for a building site and has nothing to do with a sales floor, there is no stock movement in it and no invoice, and retail selling was never built. What travels is where the record starts. Laravel takes the entries, MySQL keeps them, and the field app is written in React Native (Expo). No production planning, no supply chain, no consolidated finance; personnel files, leave and payroll also sit outside this scope.

  • No fixed reader goes on the door, so nothing has to be unbolted, carried away or rewired when a point closes.
  • The name of the point is not picked from a list: the location of the scan says which point the record belongs to.
  • The limit of what we promise is the operations record and the accounting side; personnel files, leave management and payroll are things we cannot show.

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

Construction workforce attendance — no device at the door, the entry starts on a phone

The shape of the field app follows from how long a gate stays put. A building site has an address for as long as the job lasts: the gate opens today, goes when the work ends, and people move between them. So no fixed reader went on the door. The record starts on the worker's own phone: the code scanned brings the person, the place of the scan brings the point, never a hand-picked name. An entry with no counterpart stays incomplete, and duration only comes out of a matched pair. The app is written in React Native (Expo); Laravel takes the entries, MySQL keeps them. Stock movement and invoicing were never built here.

Read the case study →

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

  • You give a building site example, but our work happens on a sales floor in Beylikduzu. What does this record say to us?

    The shared condition is that the door is not permanent. On a sales floor the entrance is the one customers use, and the point itself can move. On site we answered that with the record rather than with hardware: the scan identifies the person, the place of the scan identifies the point. The floor does not have to be a building site.

  • We run several points and staff move between them. Can the system tell them apart?

    It can, because the point is carried by the record itself. Hours worked at different points do not melt into a single total; each entry knows which point it belongs to, so they can be read separately.

  • Is this a human resources system?

    No. What we describe is how a field record is created and how it reaches the accounting side. Personnel files, leave processes, payroll and performance management fall outside this scope, and so do production planning and the supply chain.

  • Would you not have to come to our points to install it?

    No. We keep no office and give no on-site support, and there is no device to fit at a door in any case: the app runs on the worker's phone. Before we start, what we need from you is the list of your points and where each one sits, and that reaches us in writing.

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