We sell one good by the kilo, by the case and by the tin. Does each need its own product card?

It does not. In Kokudankokuya price and stock are held at volume level: the product card stays single and a size becomes a row beneath it. Opening a size is not the same as adding a product, and the figure for one good cannot split across duplicate cards.

Kokudankokuya is a perfume shop. What does it say to a wholesale food or hardware trader?

That it is perfume, plainly. What travels is not the scent but the level the record is kept at: a variant is an axis under the product rather than a separate card above it. A pack size lands in the same place.

You say ERP. Does that include accounting and current accounts?

Not in Kokudankokuya, which sits on the catalogue and stock side. The accounting chain is carried in AlgoCar, our own product, where a work order, the part consumed and the invoice are read off one record. Production planning, supply chain, consolidated finance and human resources sit outside both.

Our store is in Fatih, in the basement of a han off Tahtakale. Would you not have to come and count it?

No. We hold no office and nobody travels out to a site. What we have to settle is not where a shelf stands but which record a size is written to, and we put that down in writing together. You still walk the aisle; what the system owes you is the right row underneath the product, with the case and the tin held as separate sizes.

ERP · Fatih

ERP for Fatih businesses

Eminonu and Tahtakale are the wholesale heart of the peninsula. Sell one good in three packings — by the kilo, by the case, by the tin — and opening each as its own product card swells the item list while the price of one good drifts between the cards holding it. So the question for ERP software in Fatih, Istanbul is whether a pack size sits above the product or beneath it. Kokudankokuya settles it a level lower: price and stock sit on the volume, so adding a size opens no new product.

Get a quote Tell us about your project

ERP — Fatih

Trade in Fatih still runs on line count. In a store under a han one good stacks up in several sizes, and a guesthouse nearby splits a single service into rows by headcount. The work closest to this district's sector profile is Kokudankokuya. Where it does not overlap: it is perfume retail, so a wholesale current account or an accounting ledger is not something we can point to. What carries across is the level the record is kept at, with the sellable unit sitting under the product rather than beside it. The scope stays narrow: supply chain, production planning, human resources and consolidated finance are outside it. The shop itself stands on Laravel with MySQL behind it.

Price and stock are held at volume level, so adding a size writes a row under the product instead of opening another product.
Scent family and note run as a second axis beside the category tree, and one perfume can hang on several notes, so the same item is reached from more than one search.
Where the evidence stops is written down: Kokudankokuya carries no invoice, no current account and no accounting ledger, and what we describe is how the catalogue and the stock are shaped.

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.

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

Kokudankokuya — price and stock ride on the volume, not on a new product card

Kokudankokuya is a perfume shop. Price and stock are held at volume level, so the number of products does not grow with the number of sizes on the shelf: adding a volume opens no new catalogue entry, and one good's price cannot drift between duplicate cards because it lives in one place. Beside the category tree, scent family and note open a second way through the catalogue, and a perfume can hang on several notes at once. The shop stands on Laravel and MySQL; the catalogue needed no separate search layer. Invoicing, current accounts and the accounting ledger are outside it.

Read the case study →

Working with Fatih 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 sell one good by the kilo, by the case and by the tin. Does each need its own product card?

It does not. In Kokudankokuya price and stock are held at volume level: the product card stays single and a size becomes a row beneath it. Opening a size is not the same as adding a product, and the figure for one good cannot split across duplicate cards.
Kokudankokuya is a perfume shop. What does it say to a wholesale food or hardware trader?

That it is perfume, plainly. What travels is not the scent but the level the record is kept at: a variant is an axis under the product rather than a separate card above it. A pack size lands in the same place.
You say ERP. Does that include accounting and current accounts?

Not in Kokudankokuya, which sits on the catalogue and stock side. The accounting chain is carried in AlgoCar, our own product, where a work order, the part consumed and the invoice are read off one record. Production planning, supply chain, consolidated finance and human resources sit outside both.
Our store is in Fatih, in the basement of a han off Tahtakale. Would you not have to come and count it?

No. We hold no office and nobody travels out to a site. What we have to settle is not where a shelf stands but which record a size is written to, and we put that down in writing together. You still walk the aisle; what the system owes you is the right row underneath the product, with the case and the tin held as separate sizes.

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

ERP for Fatih businesses

ERP — Fatih

Why Algoriel

Work order through to invoice

Stock moves next to the job

The calculation becomes the quote

Where the scope stops

What we build

Work order, part and invoice on one chain

The same movement is never typed twice

Cost and revenue in one system

Spend that accumulates on the asset

Where a quote line came from

From calculation to basket to project

Work like this

Kokudankokuya — price and stock ride on the volume, not on a new product card

Working with Fatih teams, remotely

Frequently asked

We sell one good by the kilo, by the case and by the tin. Does each need its own product card?

Kokudankokuya is a perfume shop. What does it say to a wholesale food or hardware trader?

You say ERP. Does that include accounting and current accounts?

Our store is in Fatih, in the basement of a han off Tahtakale. Would you not have to come and count it?

ERP in other cities

Ankara

Istanbul

Izmir

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

ERP for Fatih businesses

ERP — Fatih

Why Algoriel

Work order through to invoice

Stock moves next to the job

The calculation becomes the quote

Where the scope stops

What we build

Work order, part and invoice on one chain

The same movement is never typed twice

Cost and revenue in one system

Spend that accumulates on the asset

Where a quote line came from

From calculation to basket to project

Work like this

Kokudankokuya — price and stock ride on the volume, not on a new product card

Working with Fatih teams, remotely

Frequently asked

We sell one good by the kilo, by the case and by the tin. Does each need its own product card?

Kokudankokuya is a perfume shop. What does it say to a wholesale food or hardware trader?

You say ERP. Does that include accounting and current accounts?

Our store is in Fatih, in the basement of a han off Tahtakale. Would you not have to come and count it?

ERP in other cities

Ankara →

Istanbul →

Izmir →

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

Ankara

Istanbul

Izmir