Get a quote

Web Software · Catalca

Web Software for Catalca businesses

If you produce or sell food in Catalca, the real question may not be whether you need a website but how much of one you can keep running yourself once the invoice is paid. Merkez Kasap is a butcher shop in Catalca and genuinely our client, and no other district gives us that. We wrote its menu, and the size of that job is easiest to describe by what we left out: no ordering, no payment, no stock.

Web Software — Catalca

The part of Catalca that overlaps with our portfolio is narrow: food production, food retail, small businesses with nobody on staff who writes software. Whoever reads the menu is at a table, on a personal phone, on whatever signal reaches inside the shop, deciding in seconds. A photo or a PDF asks for pinch and zoom, arrives late, and gets closed unread. The next break comes after launch: a price moves, and somebody has to keep the page current. In a shop with no technical staff that answer does not follow the scope, it sets it. So we built from that end: the edit stays small enough for the owner to make alone.

  • We wrote the omissions into the scope: with no ordering, payment or stock layer, no outside service has to respond before the page renders.
  • We treated the weak signal inside the shop as a constraint: the menu arrives in one load, and Vue 3 keeps it on one page, so moving between sections costs no new request.
  • We kept maintenance in the owner's reach: the menu is text, a price line is corrected in place, and the stack stops at Node.js and Vue 3.

Why Algoriel

  • Brochure and requests together

    The pages that present your business and the screens that handle incoming requests sit in one application, as they do at Diotek.

  • Listings built on the server

    Product and stock listings are assembled on the server rather than in the browser, as they are on Plastik ve Makina.

  • A second way in

    A calculator, a filter or a listing page has an address of its own, so people arrive there straight from search.

  • Every page has an address

    On Günlük Hava Durumu every date and location keeps a permanent address of its own.

What we build

Web Software
  • A web application of your own

    The parts working behind the site are built around your own way of operating: incoming requests, approvals, lists, the admin panel. At Diotek a pre-sale site survey and a post-installation service call were built as two separate flows.

  • Pages rendered on the server

    Lists and pages are assembled on the server and arrive ready to display, so nobody watches an empty screen fill itself in. Plastik ve Makina refreshes its results in place when a filter changes, rather than reloading the page.

  • Performance and findability

    Every page carries a permanent address, and headings and content come out in a form a search engine can read. Günlük Hava Durumu publishes each date and location breakdown at its own address.

  • Validation on the server

    Form validation is never left to the browser; it happens again on the server. A request that arrives outside working hours still lands in writing instead of in a phone note.

  • Catalogue and filters

    A product, listing or content catalogue follows the distinctions your own trade makes, and the filters answer questions buyers actually ask. On Plastik ve Makina new and second-hand machines share one list, with condition as a filter.

  • Life after launch

    The team that writes the application also keeps maintaining it. Adding a section, or absorbing a busier season, does not mean standing up a second system.

Work like this

Web Software · Case study

Merkez Kasap, Catalca — the smallest build in the portfolio, scoped by omission

Merkez Kasap is a butcher shop in Catalca and the smallest piece of work in our portfolio, which makes its constraints clearest. A printed menu meant a fresh print run every time a price moved. Once the menu became text that expense went away: the line is corrected in place, the code on the counter stays valid. We left ordering, payment and stock out on purpose — the shop would have paid for those layers twice, to build and to keep alive, and each would sit between the scan and the menu.

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

  • How much of a website does a small food business in Catalca need?

    Usually less than a proposal assumes. We size the work by what the shop can keep running once we step away, and write the omitted layers into the scope. Ordering, payment and stock never entered the Merkez Kasap plan.

  • You keep no office. How did you work with a business here?

    We work fully remotely, and that is the model rather than a gap in it. On Merkez Kasap we agreed what the menu had to do, what stayed out, and who would edit it later. The shop is in Catalca; the work needed nobody nearby.

  • Who updates the menu when a price changes?

    The owner, and it is an edit rather than a print job. The menu lives as text, so a corrected line is current at once behind the same QR code.

  • Could the same idea work for our business cards?

    That is what we are building in QRVizit, still in development — we describe it as work in progress, not something to buy today. The printed code's address is fixed once, while the page it opens is edited from a panel. Scanning installs nothing. Redis carries the scan load; the records stay in MySQL.

Let's work out what your site needs behind it.