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

ERP for Atasehir businesses

A package sold up front lives in two different times. The money arrives on one day; the service spreads across weeks. If your head office sits in the office blocks around Icerenkoy and keeps those two in separate lists, the end of the month turns into a reconciliation exercise. That is the knot ERP software in Atasehir, Istanbul has to untie first. At Pilatesco the invoice is raised at the sale and usage is read off the calendar, and both meet on one customer record.

Get a quote Tell us about your project

ERP — Atasehir

Atasehir is known as a finance centre and we have no client here; we say so rather than imply otherwise. Where a multi-branch company gathers reporting at the centre and sells service as a package paid for in advance, the sale and the delivery fall in different weeks; keep them in separate lists and the month closes in an argument. The work closest to that pattern is Pilatesco. The limit of the promise, plainly: Pilatesco was written for a sports and fitness business, and consolidated finance, production planning, supply chain and human resources are things we cannot show. The scope stays at the operations record, stock movement and accounting. Laravel runs the process and MySQL holds the records.

  • The invoice is raised when the package is sold, while the usage behind it is read off a calendar running for weeks and never copied into a second table.
  • The screen that sees the sale and the screen that sees the usage read the same customer record, so nothing has to be handed from a branch up to the centre.
  • A cancellation, a no-show and a completed session are handled apart from one another, and which of them returns an entitlement is set in the rule rather than in a conversation.

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

Pilatesco — the invoice is raised at the sale, usage comes off the calendar

How many people a slot holds is decided by the instructor, the equipment and the hour together, so a one-to-one session and a group class open under their own rules. The commercial side runs alongside: the invoice appears when the package is sold, while usage is read off a calendar that stretches over weeks. Two timings meet on one customer record; no second ledger is kept. A cancellation, a no-show and a completed class are each handled apart, and the rule states which one gives an entitlement back. The process runs on Laravel, with the package and booking records in MySQL.

Read the case study →

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

  • How do we see how much of a prepaid package has been used?

    Usage sits in the calendar rather than in a separate table. The invoice appears at the sale and the usage is read off that calendar; because both hang on the same customer record, no reconciliation step turns up at month end.

  • Have you worked with a financial institution with its head office in Atasehir?

    We have not. There is no bank or financial institution among our clients, and we do not write sentences on top of a reference that does not exist. What this page draws on is where Pilatesco's records line up with a pattern like that.

  • Is this an ERP or a booking system?

    Our evidence covers the link where the sale meets the usage. The calendar is one end of that chain and the invoice is the other. Production planning, supply chain and consolidated finance sit outside the promise because we have nothing to show there.

  • We run branches. How does head office reporting come out?

    The report comes off the same record, not a second ledger. The service written at a branch and the invoice read at the centre hang on one customer record, so the number the centre reads is not waiting on a file sent up from a branch.

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