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

E-Commerce · Catalca

E-Commerce for Catalca businesses

Behind a counter in Catalca a shopkeeper describes goods in the trade's own terms: the cut, the preparation, the weight. Off-the-shelf store setups leave no room for those terms in the category tree, so the product lands under a broad heading and nobody searching in their own words ever reaches it. Plastik ve Makina turns the question round. The whole tree there is built on the divisions of a single machine family, and what would be a footnote in a general catalogue becomes the division that carries the list.

Get a quote Tell us about your project

E-Commerce — Catalca

The district runs on food retail and rural trade, mostly businesses the owner works in personally. Merkez Kasap really is in Catalca, and it is the only job whose district matches its client. That job was a menu page, though — no ordering, payment or stock layer was ever built, so it proves nothing about running a store. The evidence here is Plastik ve Makina, which carries a boundary of its own: a listings platform rather than a shop, with no basket, payment or stock, the deal settled between the parties. We have never written farming or livestock software. What travels is where the catalogue is cut. The stack is a Laravel core, MySQL records, a Redis cache and a Tailwind interface.

  • The trade sets the divisions, not the catalogue: in Plastik ve Makina the tree follows one machine family's own distinctions rather than a broad industrial heading.
  • Used and new do not open two separate lists; the condition sits inside the search as an axis, and a buyer sees both options side by side.
  • The boundary is written down as well: MySQL holds the listing records and Redis takes the read load, but no basket, payment or stock layer was ever built on this platform.

Why Algoriel

  • Priced by your own unit

    If you do not sell by the piece, the records do not either: Kokudankokuya prices and stocks every volume on its own.

  • Price moves with the choice

    Trim and colour update the price on the same screen, so a buyer never opens the basket just to see a total.

  • Used stock is a filter

    New and used machinery share one listing on Plastik ve Makina, with condition as a filter instead of a second catalogue.

  • One flow through to payment

    Configuring a product and paying for it are two steps of the same flow, with no handover to another system.

What we build

E-Commerce

  • The storefront

    The shop window, product pages, search and navigation follow how your customers actually look for what you sell. At Kokudankokuya the scent family and its notes open a second route beside the category tree.

  • Configuration into checkout

    When a sale needs choices and prices moving together, payment becomes the last step of that same flow rather than a separate form. On the KGM SsangYong sales channel the price updates on screen as the buyer picks trim and colour.

  • Variants and pricing

    Price and sales conditions attach to the unit you actually sell, so a customer never rebuilds a configuration at the next step. The KGM SsangYong sales channel stores every trim and colour pairing with its own price and its own image.

  • Inventory and operations

    Stock and order information is tracked the way your team already works. Kokudankokuya keeps a scent as one product record while each volume is its own sellable unit, so adding one never means opening another product.

  • Only the parts the job needs

    We do not assume your traffic and add layers for it, because you are the one who maintains them for years. Kokudankokuya's catalogue never reached a scale that called for a separate search layer.

  • Payment and shipping connections

    The payment and shipping providers you already use connect at the same point in the sales flow. You choose who you work with, and the connection is built around that choice.

Work like this

E-Commerce · Case study

Plastik ve Makina — a category tree cut to one machine family's divisions

A trade listings platform for people buying and selling plastics processing machinery. The whole category tree follows the divisions of a single machine family, so a buyer reaches the machine using their own words for it. Used and new listings sit in one list, with condition opening as a filter axis. A seller publishes into a trade catalogue rather than under a broad industrial heading. MySQL holds the listing records, Redis takes the read load, Tailwind shapes the interfaces. The boundary is worth stating: this is not a shop. No basket, payment or stock layer was built, and the deal is settled between the parties.

Read the case study →

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

  • Do you actually have a client in Catalca?

    We do. Merkez Kasap is a business working here, and it is the only client we can name alongside a district. Let us describe the job as it was, though: we moved a paper menu onto a page opened by a QR code, and no ordering, payment or stock layer was asked for or built. That is not evidence of running a store; the evidence on this page is Plastik ve Makina.

  • Our goods are split by cut, preparation and weight. Can a catalogue carry that?

    Only if the tree is cut from those divisions. That is what we did in Plastik ve Makina: the categories came from the trade's own distinctions rather than a broad heading. The sequence with you would be the same — first we write down what the sellable unit is and which distinction becomes a filter.

  • Is Plastik ve Makina a shop?

    No, it is a listings platform. No basket, payment or stock layer was built, and the deal stays between the parties. What makes it evidence on this page is not a checkout flow but where the catalogue is cut. On a setup with a basket, that layer would be a scoping item of its own.

  • Do you also build software for farms and livestock?

    No. We have never done work in that field and we do not promise what does not exist. What we can talk about is the catalogue and listings side. We keep no office either; every job, Merkez Kasap included, is run remotely.

E-Commerce in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Let's plan your catalogue and your checkout.

Get a quote or open the service